Comment 2 for bug 1604002

Thank you for reporting this.

It is not clear from defect if the deploy had failed. If it is deploy failure,
Was it due to some failure in proliantutils calls related to setting boot mode?
Or was it due the image was capable of bios boot and failed to boot in the UEFI environment?
Is this hardware of type Gen 9?

Few comments on boot mode on iLO drivers.

Secure Boot:-
Boot mode needs to be changed to UEFI if secure boot is requested during deploy. Enabling UEFI Secure boot is a two step process and each step needs a server reset.
1. Change boot mode to UEFI. Reset server.
2. Enable UEFI secure boot. Reset server.

Trusted boot:-
Trusted boot is not being qualified on iLO drivers. It was a common change done when trusted boot feature was enabled. This condition is true for all drivers. Trusted boot is supported only in bios boot mode.

Default boot:-
When no boot mode is requested in the node/instance_info. It sets boot mode in following order:
1. Uses boot mode from node capabilities, if present.
2. Uses pending boot mode on the Node, if present.
3. Uses 'UEFI' boot mode if underlying server supports it.
4. Uses 'BIOS'