9a0fa631ca
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
9 lines
321 B
YAML
9 lines
321 B
YAML
---
|
|
fixes:
|
|
- |
|
|
When aborting cleaning, the ``last_error`` field is no longer initially
|
|
empty. It is now populated on the state transition to ``clean failed``.
|
|
- |
|
|
When cleaning or deployment fails, the ``last_error`` field is no longer
|
|
temporary set to ``None`` while the power off action is running.
|