Bug #22552
closed
Bootdisk provision method does not appear
Added by Lukas Zapletal over 6 years ago.
Updated over 6 years ago.
Description
When Foreman is started with Bootdisk plugin which registers new provision method called "bootdisk" it does not show up in hammer host create --help
command:
--provision-method METHOD Possible value(s): 'build', 'image'
The method string is properly registered in engine registry, but from here my hammer expertise ends, so filing an issue for that.
- Category changed from Hammer core to Hosts
- Difficulty set to trivial
- Blocked by Bug #22557: provision_method in host create API should list possible values in param type added
- Status changed from New to Ready For Testing
- Assignee set to Tomáš Strachota
- Pull request https://github.com/theforeman/hammer-cli-foreman/pull/354 added
- Bugzilla link set to 1544498
- Translation missing: en.field_release set to 290
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Tested with upstream build, with following packages installed:
foreman-1.18.0-0.develop.201803191746git60d7dd7.el7.noarch
tfm-rubygem-hammer_cli-0.13.pre.develop-1.201803191125git4b10ad6.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.13.pre.develop-1.201803130920git87fdd31.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-6.el7.noarch
tfm-rubygem-foreman_bootdisk-11.0.0-1.fm1_18.el7.noarch
and with enabled bootdisk via `foreman-installer --enable-foreman-plugin-bootdisk` I'm still not seeing the required update in cli or in apidoc:
- hammer host create -h | grep provision
--provision-method PROVISION_METHOD The method used to provision the host.
Possible value(s): 'build', 'image'
Discussed with tstrachota, it seems both above commits got into the build as expected. Could there be something missing on the foreman_bootdisk side?
Lukas, do you have any clue why the change didn't take effect?
Peter Ondrejka wrote:
- hammer host create -h | grep provision
--provision-method PROVISION_METHOD The method used to provision the host.
Possible value(s): 'build', 'image'
Peter, just for a case, did you refresh the apidoc cache on a client side? `hammer -r host create -h `
Yes, we checked that. The new value doesn't appear even in the api docs.
Also available in: Atom
PDF