Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Nov 25, 2024

Why

That timer was started during boot and continued regardless if rabbit was running or stopped.

This caused the reconsiliation to crash if the rabbit app was stopped before the it ended because it tried to access the database even though it was stopped or even reset.

How

We just check if rabbit is running before running one reconciliation and scheduling a new one.


This is an automatic backport of pull request #12799 done by Mergify.

[Why]
That timer was started during boot and continued regardless if `rabbit`
was running or stopped.

This caused the reconsiliation to crash if the `rabbit` app was stopped
before the it ended because it tried to access the database even though
it was stopped or even reset.

[How]
We just check if `rabbit` is running before running one reconciliation
and scheduling a new one.

(cherry picked from commit 03f9d36)
[How]
The function now accepts that the node to reset is already out of the
cluster. This avoids a mismatch exception for a situation that is ok.

(cherry picked from commit fe2061b)
@dumbbell dumbbell added this to the 4.0.5 milestone Nov 25, 2024
@dumbbell dumbbell merged commit f82fd40 into v4.0.x Nov 25, 2024
195 checks passed
@dumbbell dumbbell deleted the mergify/bp/v4.0.x/pr-12799 branch November 25, 2024 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants