aca8ebc064
No exception is used to communicate back, the exceptions are used to catch failures, and if we don't catch other possible exceptions leaving cleaning states, we may not clean up state properly. So instead of specific exceptions, we just catch any exception like is used earlier in the same method. Inspired by https://review.opendev.org/c/openstack/ironic/+/866856 and investigation through the code base as a result of inability to clean the node. Change-Id: I2a6bca3550819b98adbaffe315f77427b8a43d62
9 lines
361 B
YAML
9 lines
361 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue where unexpected exceptions coming from the process to
|
|
start cleaning would not trigger the cleaning_error_handler which
|
|
performs the needful internal resets to permit cleaning to be retried
|
|
again in the future. Now any error which is encountered during the
|
|
launch of cleaning will trigger the error handler.
|