ROX-34019: Revert change to VulnMgmtTest RHEL image#19877
Merged
Conversation
|
Skipping CI for Draft Pull Request. |
Contributor
Author
|
/test all |
Contributor
🚀 Build Images ReadyImages are ready for commit 811f960. To use with deploy scripts: export MAIN_IMAGE_TAG=4.11.x-596-g811f960e66 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #19877 +/- ##
==========================================
- Coverage 49.58% 49.58% -0.01%
==========================================
Files 2766 2766
Lines 208530 208540 +10
==========================================
+ Hits 103406 103408 +2
- Misses 97451 97460 +9
+ Partials 7673 7672 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
d05b1d0 to
0052ecc
Compare
0052ecc to
ba55ab0
Compare
charmik-redhat
approved these changes
Apr 8, 2026
Contributor
Author
|
/test gke-nongroovy-e2e-tests |
Contributor
|
/retest |
clickboo
approved these changes
Apr 8, 2026
BradLugo
approved these changes
Apr 8, 2026
janisz
approved these changes
Apr 8, 2026
janisz
added a commit
that referenced
this pull request
Apr 8, 2026
Added PR reference tracking to show which PRs link to each Jira issue that has missing metadata. Example output: - ROX-33451: ✗ fixVersion, ✗ affectedVersion (Assignee: ..., Team: ..., Component: ...) (PRs: #19382) - ROX-34000: ✗ fixVersion, ✗ affectedVersion (Assignee: ..., Team: ..., Component: ...) (PRs: #19876, #19877) Implementation: - Track jira_key → PR numbers mapping while checking metadata - Include PR links at end of Jira issue line - Multiple PRs shown as comma-separated list with links Makes it easier to identify which PRs need Jira metadata updates. Partially generated with AI assistance.
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
6 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.
Description
#19642 updated the test images used to work for both Scanner V2 and V4, this caused e2e tests to flake (see ROX-34019)
This is a legit bug in Scanner V2 that older images tested would not encounter (see ROX-34058)
The bug randomly causes the scan to yield no results, was able to reproduce by repeatedly scanning the test image, and clearing scanner-db image tables in-between attempts.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
CI