Bug 2135615

The default boot mode for 17.0 is now UEFI boot, so our first recommendation would be to switch the nodes from Legacy BIOS to UEFI boot so that boot modes are aligned.

We recommend boot mode UEFI where possible but there may be some environments which still need to use Legacy BIOS. If you must use Legacy BIOS you'll need to ensure that the "capabilities" attribute for each baremetal node includes  boot_mode:bios. This can be set with a command like:

  NODE=<NODE NAME OR ID> ; openstack baremetal node set --property capabilities="boot_mode:bios,$(openstack baremetal node show $NODE -f json -c properties | jq -r .properties.capabilities | sed "s/boot_mode:[^,]*,//g")" $NODE

This *might* allow overcloud-hardened-uefi-full to boot in Legacy BIOS but we may not be able to provide support if there are issues with this combination. This is why we still distribute the overcloud-full partition image, which you may need to use instead of overcloud-hardened-uefi-full.

Please let us know which approach was successful.

(In reply to Steve Baker from comment #1)
> The default boot mode for 17.0 is now UEFI boot, so our first recommendation
> would be to switch the nodes from Legacy BIOS to UEFI boot so that boot
> modes are aligned.

Yes Steve you are right. I am using VM on KVM & seems it requires additional config to enable UEFI compared to bios which is default. 
overcloud-hardened image is working fine having boot_mode as UEFI.
> 
> We recommend boot mode UEFI where possible but there may be some
> environments which still need to use Legacy BIOS. If you must use Legacy
> BIOS you'll need to ensure that the "capabilities" attribute for each
> baremetal node includes  boot_mode:bios. This can be set with a command like:

> 
>   NODE=<NODE NAME OR ID> ; openstack baremetal node set --property
> capabilities="boot_mode:bios,$(openstack baremetal node show $NODE -f json
> -c properties | jq -r .properties.capabilities | sed
> "s/boot_mode:[^,]*,//g")" $NODE
> 
> This *might* allow overcloud-hardened-uefi-full to boot in Legacy BIOS but
> we may not be able to provide support if there are issues with this
> combination. 

hardened image+bios combination is not working where overcloud node was booted & stuck is rescue mode as mentioned in the description.
Anyways since there is no support for hardened+bios combination so will avoid to use.


This is why we still distribute the overcloud-full partition
> image, which you may need to use instead of overcloud-hardened-uefi-full.
> 
> Please let us know which approach was successful.

overcloud-full partition image is working fine with bios.

I just attempted to deploy overcloud-hardened-uefi-full+BIOS directly as a VM (no ironic, no agent deploy) and it booted fine, so I think the image artifact itself is capable of booting in Legacy BIOS mode. I think we're seeing some interaction with ironic-python-agent deploying a whole disk with Legacy BIOS. I'll get set up to try that.

I've just successfully deployed overcloud-hardened-uefi-full to a baremetal node in Legacy BIOS boot mode with ironic. Both the overcloud-hardened-uefi-full and ironic-python-agent images are the latest 17.0 images[1].

I'm going to close this on the basis that overcloud-hardened-uefi-full is capable of deploying with Legacy BIOS, and any specific environment where this fails can be directed to deploy either overcloud-hardened-uefi-full+UEFI or overcloud-full+BIOS.

*** This bug has been marked as a duplicate of bug 2138046 ***

Changing this to being a duplicate, bug #2138046 has lead to the root cause of overcloud-hardened-uefi-full+BIOS not working