When deploy is requested for by setting instance_info/capabilities with secure_boot='true', the code oevrwrites the capabilities in the node/properties.
Steps to reproduce:- $ ironic node-update $NODE remove properties $ ironic node-update $NODE add instance_info/image_source=$UBUNTU_CLOUD_IMAGE instance_info/root_gb=5 $ ironic node-update $NODE add instance_info/capabilities='{"secure_boot":"true"}' $ ironic node-set-provision-state $NODE active
$ ironic node-show $NODE | grep properties | properties | {u'capabilities': u'boot_mode:uefi'}
It should not update the 'boot_mode' in properties/capabilities, but should internally take it as the uefi boot mode.
When deploy is requested for by setting instance_ info/capabiliti es with secure_boot='true', the code oevrwrites the capabilities in the node/properties.
Steps to reproduce:- info/image_ source= $UBUNTU_ CLOUD_IMAGE instance_ info/root_ gb=5 info/capabiliti es='{"secure_ boot":" true"}' provision- state $NODE active
$ ironic node-update $NODE remove properties
$ ironic node-update $NODE add instance_
$ ironic node-update $NODE add instance_
$ ironic node-set-
$ ironic node-show $NODE | grep properties
| properties | {u'capabilities': u'boot_mode:uefi'}
It should not update the 'boot_mode' in properties/ capabilities, but should internally take it as the uefi boot mode.