iLO drivers: Inconsistent boot mode default value
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Medium
|
Shivanand Tendulker | ||
tripleo |
Fix Released
|
Medium
|
Dmitry Tantsur |
Bug Description
From a downstream bug report: https:/
When no boot mode is explicitly passed to the iLO drivers (via flavor/
One interesting thing is that, the documentation [1] says that "If the pending boot mode is not set on the node then iLO drivers use ‘uefi’ boot mode for UEFI capable servers and “bios” when UEFI is not supported.". So, the boot mode gets set to UEFI if the node is "UEFI capable" instead of checking if UEFI is actually enabled for that node making it fail to deploy (as per downstream bug, see above)
To summarize, the "magic" in choosing the default value for boot mode in the iLO drivers is the source of a lot of pain for users and developers that have to troubleshoot errors it may cause. This behavior also causes the iLO driver to be inconsistent with all other drivers in tree that assumes "bios" if no boot mode is set on the flavor/
[1] http://
Changed in ironic: | |
importance: | Undecided → Medium |
summary: |
- iLO drivers: Inconsistent boot mode default values + iLO drivers: Inconsistent boot mode default value |
description: | updated |
description: | updated |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Dmitry Tantsur (divius) |
Changed in tripleo: | |
milestone: | none → ocata-1 |
At the very least we need a configuration option for this default.. However, we might need to change it completely.