summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorJulia Kreger <juliaashleykreger@gmail.com>2022-12-07 11:56:32 -0800
committerJulia Kreger <juliaashleykreger@gmail.com>2022-12-12 07:22:21 -0800
commitaca8ebc0640cbef5eb9fa898be08dfe8d3a0f4ae (patch)
tree2bb841c45d71767474202fdda12ca5f871aafa10 /releasenotes
parent4d66609e95a1c7f5fb0fe0f61f95cf83d09da4d8 (diff)
downloadironic-aca8ebc0640cbef5eb9fa898be08dfe8d3a0f4ae.tar.gz
Catch any exception for Cleaning
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
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/catch-all-cleaning-exceptions-1317a534a1c9db56.yaml8
1 files changed, 8 insertions, 0 deletions
diff --git a/releasenotes/notes/catch-all-cleaning-exceptions-1317a534a1c9db56.yaml b/releasenotes/notes/catch-all-cleaning-exceptions-1317a534a1c9db56.yaml
new file mode 100644
index 000000000..eb3cc61f9
--- /dev/null
+++ b/releasenotes/notes/catch-all-cleaning-exceptions-1317a534a1c9db56.yaml
@@ -0,0 +1,8 @@
+---
+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.