OCPBUGS-76394: Ignore group ownership on rpm -V#2206
Conversation
What's happening is since we're removing subscription-manager from the base image and a subsequent step writes the file with group ownership that differs from what's defined in subscription-manager rpm it fails verification. The intent of this command seems to be to ensure that all requested rpms are installed so group ownership doesn't seem critical to verify here.
openshift-ci-robot
added
jira/valid-reference
|
@sdodson: This pull request references Jira Issue OCPBUGS-76394, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
WalkthroughThe Dockerfile for the tools image has been updated to add the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches
🧪 Generate unit tests (beta)
Comment |
|
/jira refresh FWIW, I intend to merge this once it passes CI. |
openshift-ci-robot
added
jira/valid-bug
|
@sdodson: This pull request references Jira Issue OCPBUGS-76394, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
/verified by CI |
openshift-ci-robot
added
the
verified
|
@sdodson: This PR has been marked as verified by DetailsIn response to this:
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. |
|
/override ci/prow/e2e-aws-ovn-serial-1of2 ci/prow/e2e-aws-ovn-serial-1of2 ci/prow/e2e-aws-ovn-upgrade |
|
/lgtm |
|
@sdodson: This pull request references Jira Issue OCPBUGS-76394, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
There is another indirectly related PR, just for awareness #2205 |
|
@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-ovn-serial-1of2, ci/prow/e2e-aws-ovn-upgrade DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ardaguclu, sdodson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
Thanks for the pointer and also for quick review on these, I think these two can go forward without conflict. |
|
/override ci/prow/e2e-agnostic-ovn-cmd ci/prow/e2e-aws-ovn ci/prow/e2e-aws-serial-2of2 |
|
@sdodson: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn response to this:
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. |
|
/override ci/prow/e2e-agnostic-ovn-cmd ci/prow/e2e-aws-ovn ci/prow/e2e-aws-ovn-serial-2of2 |
|
@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-agnostic-ovn-cmd, ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-serial-2of2 DetailsIn response to this:
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. |
sdodson
added
the
acknowledge-critical-fixes-only
|
@sdodson: Jira Issue Verification Checks: Jira Issue OCPBUGS-76394 Jira Issue OCPBUGS-76394 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-02-21-040517 |
|
/cherry-pick release-4.21 release-4.20 |
|
@sdodson: new pull request created: #2208 DetailsIn response to this:
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. |
5 participants
What's happening is since we're removing subscription-manager from the base image and a subsequent step write
/etc/yum.repos.d/redhat.repowith group ownership that differs from what's defined in subscription-manager rpm it fails verification. The intent of this command seems to be to ensure that all requested rpms are installed so group ownership doesn't seem critical to verify here.Note: subscription-manager doesn't actually deliver /etc/yum.repos.d/redhat.repo but it does lay claim to it via its rpm file list.
Summary by CodeRabbit