From 587dca1971109ded4c70dcbcbe868dd574f42e20 Mon Sep 17 00:00:00 2001 From: Afonne-CID Date: Mon, 4 Aug 2025 21:18:02 +0100 Subject: [PATCH] Follow-up: Clear `last_error` on power match/sync Adds a release note for the fix in patch 955432. Related-Change: https://review.opendev.org/c/openstack/ironic/+/955432 Change-Id: I2703e91ee4a3bdb65a17d5ad8511fdc909ee2262 Signed-off-by: Afonne-CID --- ...-stale-last-error-on-power-sync-689bdc3b317d5784.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/clear-stale-last-error-on-power-sync-689bdc3b317d5784.yaml diff --git a/releasenotes/notes/clear-stale-last-error-on-power-sync-689bdc3b317d5784.yaml b/releasenotes/notes/clear-stale-last-error-on-power-sync-689bdc3b317d5784.yaml new file mode 100644 index 0000000000..9d95ec880e --- /dev/null +++ b/releasenotes/notes/clear-stale-last-error-on-power-sync-689bdc3b317d5784.yaml @@ -0,0 +1,9 @@ +--- +fixes: + - | + When power state synchronization confirms or restores the expected state, + the ``last_error`` field may retain stale messages, giving a misleading + impression of failure on an otherwise healthy node. If + ``[conductor]node_history`` is enabled, the field is now cleared, + ensuring status reflects current node health while preserving error + history.