Skip to content

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

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.21from
marmijo:rhaos-pkgs-exception
Feb 28, 2026
Merged

[release-4.21] NO-JIRA: rhaos-pkgs-match-openshift: exclude known package mismatches#1889
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.21from
marmijo:rhaos-pkgs-exception

Conversation

@marmijo
Copy link
Contributor

@marmijo marmijo commented Jan 16, 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 also backports 1abf0f6

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

@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

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 16, 2026
@marmijo marmijo marked this pull request as draft January 21, 2026 07:26
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 21, 2026
@travier
Copy link
Member

travier commented Jan 26, 2026

I think this one is ready now that the one for master got merged?
/lgtm
/retest
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 26, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 26, 2026
marmijo and others added 2 commits February 27, 2026 13:44
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 exclude the conmon-rs package and 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 rhaos-pkgs-exception branch from 9faa3a3 to e21822e Compare February 27, 2026 20:48
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2026
@marmijo marmijo marked this pull request as ready for review February 27, 2026 20:48
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 27, 2026
@openshift-ci openshift-ci bot requested a review from cgwalters February 27, 2026 20:49
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 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.

Copy link
Contributor

@prestist prestist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/LGTM

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 27, 2026
Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dustymabe
Copy link
Member

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 28, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustymabe, marmijo, prestist, travier

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:
  • OWNERS [dustymabe,marmijo,prestist,travier]

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

@dustymabe
Copy link
Member

/verified by @marmijo

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 28, 2026
@openshift-ci-robot
Copy link

@dustymabe: This PR has been marked as verified by @marmijo.

Details

In response to this:

/verified by @marmijo

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.

@dustymabe dustymabe added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 28, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit d36a4d9 into openshift:release-4.21 Feb 28, 2026
3 checks passed
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants