5db194c503
When mixing in-band out-of-band steps, the out-of-band status polling flag was not being cleared, and was being left to remain in the node driver_internal_info field, thus preventing future heartbeat operations from the baremetal node from being processed to check the actual completion status of a step. We now always clear the field based upon the workflow in-progress before starting a new step and should asynchronous steps also be recorded as a result of any step's actions such as if a reboot is required. Special thanks goes to keekz for promptly providing upstream with the information necessary for us to identify the root cause. Closes-Bug: 2096938 Change-Id: I5198d9169cff8474c7a990332639b2d0758e6e1a
14 lines
726 B
YAML
14 lines
726 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue where operators executing complex arrangement of steps
|
|
which include out-of-band and in-band steps, for example a hardware
|
|
RAID ``create_configuration`` step followed by in-band steps inside of
|
|
the agent, would effectively get the agent stuck in a ``wait`` state in
|
|
the Cleaning, Servicing, or Deploying workflows.
|
|
This was related to the way out-of-band steps are executed and monitored.
|
|
Ironic, before starting to execute a new step, now cleans the polling
|
|
lockout flag for the respective workflow being executed to prevent the
|
|
agent from getting stuck. For more information, please see
|
|
`bug 2096938 <https://bugs.launchpad.net/ironic/+bug/2096938>`_.
|