2411779ee8
When doing firmware updates for BMC, we saw cases where Ironic wouldn't be able to contact the BMC, marking the node in a failed state because of it. This patch adds a configuration option that tell for how long ironic should wait before proceeding with the reboot to finish the update. We will attempt to improve the waiting time in a follow-up, trying to identify when the bmc was unresponsive and when it was back. Closes-Bug: #2092398 Change-Id: I53ffc8a06d5af8b0751553c3d4a9bb1c000027ae Signed-off-by: Iury Gregory Melo Ferreira <imelofer@redhat.com>
14 lines
666 B
YAML
14 lines
666 B
YAML
---
|
|
fixes:
|
|
- |
|
|
[`Bug 2092398 <https://bugs.launchpad.net/ironic/+bug/2092398>`_]
|
|
Fixes an issue with node servicing/cleaning that caused the node to enter
|
|
into `service failed` or `clean failed` state after doing a bmc firmware
|
|
update, due to the BMC being unresponsive to requests during the update.
|
|
Now when doing a BMC update, we wait some time before proceeding with the
|
|
reboot to finish the update.
|
|
The time is configurable and can be changed via the config option
|
|
``[redfish]firmware_update_wait_unresponsive_bmc`` (default, 300 seconds)
|
|
or by setting ``firmware_update_unresponsive_bmc_wait`` in the
|
|
``driver-info``.
|