ROX-33865: Scanner V4 retry initial DB connection#21856
Open
rhacs-bot wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
area/scanner
backport
Contributor
Author
|
Images are ready for the commit at 1cff382. To use with deploy scripts, first |
|
@rhacs-bot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
dcaravel
added
the
auto-retest
Contributor
|
/retest |
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.
Backport 0f13ca6 from #19761.
@dcaravel - this is to address the breakage in compatibility tests (
gke-nongroovy-compatibility-testsandgke-version-compatibility-tests) that started occurring after enabling Scanner V4 in CI - these tests will continue to fail on commits merged to master (and nightlies) until this is merged and subsequent tag4.9.xcreated. Indexer/matcher will restart when Scanner V4 DB does not accept the initial connection, and this triggers CI failure because the 'restart' pattern is not accepted.Until that next tag is created, also adding a pattern to
scripts/ci/logcheck/restart-ok-patterns.jsonin master to sto pthe failures until the next tag is ready, at which point will remove the pattern.