6487b95813
We have discovered hardware that only applies boot mode / secure boot changes during a reboot. Furthermore, the same hardware cannot update both at the same time. To err on the safe side, reboot and wait for the value to change if it's not changed immediately. Co-Authored-By: Jacob Anders <janders@redhat.com> Change-Id: I318940a76be531f453f0f5cf31a59cba16febf57
21 lines
958 B
YAML
21 lines
958 B
YAML
---
|
|
fixes:
|
|
- |
|
|
While updating boot mode or secure boot state in the Redfish driver,
|
|
the node is now rebooted if the change is not detected on the System
|
|
resource refresh. Ironic then waits up to
|
|
``[redfish]boot_mode_config_timeout`` seconds until the change is applied.
|
|
upgrade:
|
|
- |
|
|
Changing the boot mode or the secure boot state via the direct API
|
|
(``/v1/nodes/{node_ident}/states/boot_mode`` and
|
|
``/v1/nodes/{node_ident}/states/secure_boot`` accordingly) may now
|
|
result in a reboot. This happens when the change cannot be applied
|
|
immediately. Previously, the change would be applied whenever the next
|
|
reboot happens for any unrelated reason, causing inconsistent behavior.
|
|
issues:
|
|
- |
|
|
When boot mode needs to be changed during provisioning, an additional
|
|
reboot may happen on certain hardware. This is to ensure consistent
|
|
behavior when any boot setting change results in a separate internal job.
|