Skip to content

Remove duplicate libpciaccess from ironic lockfile#10350

Open
redhat-ship-help wants to merge 1 commit intoopenshift-eng:openshift-5.0from
redhat-ship-help:ship-help/fix-ironic-duplicate-libpciaccess
Open

Remove duplicate libpciaccess from ironic lockfile#10350
redhat-ship-help wants to merge 1 commit intoopenshift-eng:openshift-5.0from
redhat-ship-help:ship-help/fix-ironic-duplicate-libpciaccess

Conversation

@redhat-ship-help
Copy link
Copy Markdown

libpciaccess was added twice to the cachi2 lockfile RPM list in ironic.yml: first in commit 7cf7bd1 and again in PR #10092. This removes the duplicate entry and fixes the alphabetical ordering (libnsl2 before libpciaccess).

Identified during a cross-branch drift analysis of openshift-4.23 vs openshift-5.0.

libpciaccess was added twice to the cachi2 lockfile RPM list: first
in commit 7cf7bd1 and again in PR openshift-eng#10092. This removes the duplicate
entry and fixes the alphabetical ordering (libnsl2 before libpciaccess).
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tonyxrmdavidson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 1, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

Hi @redhat-ship-help. Thanks for your PR.

I'm waiting for a openshift-eng member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

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

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant