Skip to content

[Backport release-1.34] Requeue Autopilot signal node updates on conflict#7031

Merged
juanluisvaladas merged 1 commit intorelease-1.34from
backport-6994-to-release-1.34
Jan 27, 2026
Merged

[Backport release-1.34] Requeue Autopilot signal node updates on conflict#7031
juanluisvaladas merged 1 commit intorelease-1.34from
backport-6994-to-release-1.34

Conversation

@k0s-bot
Copy link
Copy Markdown
Contributor

@k0s-bot k0s-bot commented Jan 27, 2026

Automated backport to release-1.34, triggered by a label in #6994.
See .

Plans execution can stall when the plan state handler fails to update a
signal node. Detect such conflicts, log them, and flag them for retries
instead.

Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
(cherry picked from commit 79a6a86)
@k0s-bot k0s-bot requested review from a team as code owners January 27, 2026 10:09
@twz123 twz123 added bug Something isn't working component/autopilot backport/release-1.33 PR that needs to be backported/cherrypicked to the release-1.33 branch labels Jan 27, 2026
@juanluisvaladas juanluisvaladas merged commit 3505433 into release-1.34 Jan 27, 2026
203 of 204 checks passed
@juanluisvaladas juanluisvaladas deleted the backport-6994-to-release-1.34 branch January 27, 2026 11:53
@k0s-bot
Copy link
Copy Markdown
Contributor Author

k0s-bot commented Jan 27, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/release-1.33 PR that needs to be backported/cherrypicked to the release-1.33 branch bug Something isn't working component/autopilot

3 participants