diff options
| author | Dmitry Tantsur <dtantsur@protonmail.com> | 2023-02-22 16:08:09 +0100 |
|---|---|---|
| committer | Dmitry Tantsur <dtantsur@protonmail.com> | 2023-03-02 18:47:09 +0000 |
| commit | 7ea86a8669ddcba70b9a3ca05f54ebd341446097 (patch) | |
| tree | 4dc196ee67e8aeefb77ff6d3a0e8aa8be7c4dfed /.gitignore | |
| parent | 9dad023db856d9e623d56d9d77a70648b4071a40 (diff) | |
| download | ironic-7ea86a8669ddcba70b9a3ca05f54ebd341446097.tar.gz | |
Do not move nodes to CLEAN FAILED with empty last_error
When cleaning fails, we power off the node, unless it has been running
a clean step already. This happens when aborting cleaning or on a boot
failure. This change makes sure that the power action does not wipe
the last_error field, resulting in a node with provision_state=CLEANFAIL
and last_error=None for several seconds. I've hit this in Metal3.
Also when aborting cleaning, make sure last_error is set during
the transition to CLEANFAIL, not when the clean up thread starts
running.
While here, make sure to log the current step in all cases, not only
when aborting a non-abortable step.
Change-Id: Id21dd7eb44dad149661ebe2d75a9b030aa70526f
Story: #2010603
Task: #47476
(cherry picked from commit 9a0fa631ca53b40f4dc1877a73e65ded8ac37616)
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions