Skip to content

[release-4.20] NO-JIRA: rhaos-pkgs-match-openshift: exclude known package mismatches#1920

Open
marmijo wants to merge 2 commits intoopenshift:release-4.20from
marmijo:release-4.20-rhaos-pkgs-backport
Open

[release-4.20] NO-JIRA: rhaos-pkgs-match-openshift: exclude known package mismatches#1920
marmijo wants to merge 2 commits intoopenshift:release-4.20from
marmijo:release-4.20-rhaos-pkgs-backport

Conversation

@marmijo
Copy link
Copy Markdown
Contributor

@marmijo marmijo commented Mar 31, 2026

Introduce RHAOS_PACKAGE_EXCEPTIONS and build a regex from it to filter out packages that are known to not match the target version of openshift. Use a list-based structure so additional packages can be excluded in the future by appending to the exception array.

Exclude the toolbox and conmon rhaos packages, which are not expected to match.

Also remove the rhaos-pkgs-match-openshift test from the denylist.

See: #1847

This backports:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@marmijo: This pull request explicitly references no jira issue.

Details

In response to this:

Introduce RHAOS_PACKAGE_EXCEPTIONS and build a regex from it to filter out packages that are known to not match the target version of openshift. Use a list-based structure so additional packages can be excluded in the future by appending to the exception array.

Exclude the toolbox and conmon rhaos packages, which are not expected to match.

Also remove the rhaos-pkgs-match-openshift test from the denylist.

See: #1847

This backports:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 31, 2026
@openshift-ci openshift-ci bot requested review from jlebon and jmarrero March 31, 2026 22:16
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 31, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marmijo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026
@marmijo marmijo force-pushed the release-4.20-rhaos-pkgs-backport branch 3 times, most recently from 95d046e to bef29b8 Compare March 31, 2026 22:24
marmijo and others added 2 commits March 31, 2026 16:33
Introduce `RHAOS_PACKAGE_EXCEPTIONS` and build a regex from it to filter
out packages that are known to not match the target version of
openshift. Use a list-based structure so additional packages can be
excluded in the future by appending to the exception array.

Exclude the toolbox rhaos package, which is known to not match the
target version of openshift.

Also remove the rhaos-pkgs-match-openshift test from the denylist.

See: openshift#1847

This backports openshift@ef8a3bb
and part of openshift@3f11128
The build-node-image job only tests tags with the openshift tag
and any tests still in this repo should be running so let's add
the openshift tag to them.
@marmijo marmijo force-pushed the release-4.20-rhaos-pkgs-backport branch from bef29b8 to 29092e3 Compare March 31, 2026 22:34
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 31, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 31, 2026

@marmijo: all tests passed!

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants