Make legacy resume test assert data-node readiness, not LB health#864
Merged
Conversation
tomach
marked this pull request as ready for review
July 20, 2026 12:04
tomach
force-pushed
the
ta/fix-resume-test
branch
from
July 21, 2026 07:54
84f89e5 to
cc9c26c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
The end-to-end health check reaches CrateDB through the Azure load balancer, which is deleted on suspend and re-provisioned on resume, its new IP is often not routable yet, making the check flaky. Assert the data StatefulSet scales back up instead.
Checklist
CHANGES.rst