ROX-33865: Scanner V4 retry initial DB connection#21856
Conversation
|
Images are ready for the commit at 1cff382. To use with deploy scripts, first |
|
@rhacs-bot: The following test 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. |
|
/retest |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-4.9 #21856 +/- ##
============================================
Coverage 48.89% 48.89%
============================================
Files 2719 2719
Lines 202983 202989 +6
============================================
+ Hits 99252 99255 +3
- Misses 95966 95969 +3
Partials 7765 7765
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.