Skip to content

ROX-33865: Scanner V4 retry initial DB connection#21856

Open
rhacs-bot wants to merge 1 commit into
release-4.9from
backport-19761-to-release-4.9
Open

ROX-33865: Scanner V4 retry initial DB connection#21856
rhacs-bot wants to merge 1 commit into
release-4.9from
backport-19761-to-release-4.9

Conversation

@rhacs-bot

@rhacs-bot rhacs-bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Backport 0f13ca6 from #19761.

@dcaravel - this is to address the breakage in compatibility tests (gke-nongroovy-compatibility-tests and gke-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 tag 4.9.x created. 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.json in master to sto pthe failures until the next tag is ready, at which point will remove the pattern.

@rhacs-bot
rhacs-bot requested a review from a team as a code owner July 21, 2026 22:11
@github-actions github-actions Bot added area/scanner backport PR to backport changes from master to release branch labels Jul 21, 2026
@rhacs-bot

Copy link
Copy Markdown
Contributor Author

Images are ready for the commit at 1cff382.

To use with deploy scripts, first export MAIN_IMAGE_TAG=4.9.10-rc.0-4-g1cff382f86.

@openshift-ci

openshift-ci Bot commented Jul 22, 2026

Copy link
Copy Markdown

@rhacs-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/ocp-4-21-scanner-v4-install-tests 1cff382 link false /test ocp-4-21-scanner-v4-install-tests

Full PR test history. Your PR dashboard.

Details

Instructions 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 dcaravel added the auto-retest PRs with this label will be automatically retested if prow checks fails label Jul 22, 2026
@dcaravel

Copy link
Copy Markdown
Contributor

/retest

@codecov

codecov Bot commented Jul 22, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.89%. Comparing base (1b4e147) to head (1cff382).

Files with missing lines Patch % Lines
scanner/datastore/postgres/connect.go 0.00% 9 Missing ⚠️
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           
Flag Coverage Δ
go-unit-tests 48.89% <0.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/scanner auto-retest PRs with this label will be automatically retested if prow checks fails backport PR to backport changes from master to release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants