Red Hat Bugzilla – Bug 1249836
[RFE] openstack baremetal configure boot needs an image suffix option
Last modified: 2017-07-03 19:10:13 EDT
Currently when you run openstack baremetal configure boot it will look for images with fixed names (overcloud-full, bm-deploy) and configure the ironic machines to use those images It would be good to have the ability to specify an image suffix to the command and the tool will look for images with that suffix and use them instead. E.g. openstack baremetal configure boot 2015-06-30.1 Would use the images bm-deploy-kernel-2015-06-30.1 bm-deploy-ramdisk-2015-06-30.1 overcloud-full-2015-06-30.1 overcloud-full-initrd-2015-06-30.1 overcloud-full-vmlinuz-2015-06-30.1 That way we can start to allow people to utilise multiple images inside the undercloud glance, to do testing and rollback of new/old images Regards, Graeme
More generic way was chosen - added options to specify kernel and ramdisk image names.
In the scenarion when use run the --deploy-ramdisk and the --deploy-kernel in two different commands the second image is changed back to default Reproduce: 1. set deploy ramdisk --deploy-ramdisk my-ramdisk *deployed_ramdisk of ironic node is changed 2. set deploy kernel --deploy-kernel my-kernel * deployed_kernel of ironic node is changed ** deployed_ramdisk of ironic node is changed back to bm-deploy-ramdisk
This behaviour happends because both arguments (--deploy-ramdisk and --deploy-kernel) have a default value, which "changes back" the unused argument. I don't think this is a failure. Anyway we need clarify it.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Has this actually been implemented in OSP 8? I'm reading the comments and it looks like some functionality was implemented, but I'm not entirely sure Regards, Graeme
This was implemented (is in upstream). The bug failed QA because, I believe, misunderstanding, so I added needinfo there. Marek
Hi folks, I believe this feature was done long ago, and it's fair to request both arguments to be provided. If you think it's a UX problem, please open another report.