iLO does not utilize the UEFI capability for cleaning
Bug #1559835 reported by
Purandhar Sairam Mannidi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Medium
|
Mallikarjuna Reddy Kolagatla |
Bug Description
When a baremetal node is registered with any ilo driver with boot mode as UEFI, change the provision state from available to manage and then to provide.
Before registering a node, make sure the node boot mode is set to BIOS.
When the provision state is changed from available to provide, cleaning process is initiated and it is expected that the node is first changed to UEFI boot mode and boot with UEFI capable deploy images.
It is observed that irrespective of boot mode passed during the node registration, node is trying to boot with existing boot mode which in this case is BIOS and fails to boot with deploy images as they are EFI boot only.
Changed in ironic: | |
assignee: | nobody → Shivanand Tendulker (stendulker) |
Changed in ironic: | |
status: | New → Confirmed |
tags: | added: uefi |
To post a comment you must log in.
The 'boot_mode' set in the node->propertie s->capabilities is meant for deploy. Any of these properties cannot be safely used for setting boot mode during cleaning. There could be contradictory capability values. Say 'trusted_boot=true' with 'boot_mode=bios'. If required driver would need to carve out new 'driver_info' property say, 'cleaning_ boot_mode' to be used during cleaning operation. But again this would be per node basis and adds to operator overhead without much of benefit as there are no boot mode specific tasks.
Anyways, iLO driver do provide 'iso' element in DIB to create bios cum uefi bootable iso to avoid such complication of setting per node boot mode for cleaning operations.