test(itest): capture drainage state on integration-test failure [DO N… - #552
Open
tomba7 wants to merge 2 commits into
Open
test(itest): capture drainage state on integration-test failure [DO N…#552tomba7 wants to merge 2 commits into
tomba7 wants to merge 2 commits into
Conversation
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
1 participant
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.
Note: This is diagnostic code for testing the CI pipeline and will not be merged
Triage instrumentation for #542. The failure only says "timeout waiting for
deployment", which does not say why the controller declined to create the
version. This logs the state to check whether a version stuck in Draining ever recovers
controller's current/target, each deprecated version's EligibleForDeletion
bit and the ineligible count against the cap.
drainage transitions plus whether the Deployment eventually appears.
Local finding so far: under fsync throttling, one version latches in Draining
with zero transitions in 5 minutes while its siblings drain normally. When the
latched version is the 0 replica one, the ineligible count hits the cap and
the controller silently refuses the rollout which is what is seen on the CI