Conversation
CI installs MicroShift by building RPMs from source and installing them via a --repofrompath local repository. Once microshift RPMs became available in the rhocp-4.21 product repository with a release version (e.g. 4.21.29-...) that sorts higher than the locally built nightly version, dnf silently resolved 'microshift' from the product repository instead of the local one. As a result, CI jobs tested the released RPM (pinning an outdated ovn-kubernetes image affected by OCPBUGS-105440) instead of the RPMs built from the checked-out source, causing all release-4.21 conformance jobs to permafail with 'failed to get ofport of -ex' even after the fix merged. Set the highest repository priority on the local repository so dnf always prefers the locally built RPMs regardless of version ordering. Assisted-By: Claude Fable 5
openshift-ci-robot
added
the
jira/valid-reference
|
@mkowalski: This pull request explicitly references no jira issue. 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. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mkowalski The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
This fix is correct and addresses the root cause of the 4.21 nightly permafail (and a latent issue on all branches). The problem: The The fix: Tracked in USHIFT-7489. AI-generated. Review for accuracy. |
|
@mkowalski: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Replaced by #7264 |
|
@pacevedom: Closed this PR. 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. |
4 participants
What
Set
priority=1on themicroshift-localrepository used byconfigure-vm.shso dnf always installs the locally built RPMs instead of anymicroshiftRPMs published in enabled product repositories.Same change as #7257 (release-4.21), applied to this branch since the script is identical here and equally exposed.
Why
On release-4.21, all conformance CI jobs permafailed because dnf resolved
microshiftfromrhocp-4.21-for-rhel-9-x86_64-rpms(released NEVRA4.21.29-...sorts higher than the locally built nightly version) instead of the source-built RPMs in the--repofrompathlocal repo. The released RPM pins an outdated ovn-kubernetes image (missing the OCPBUGS-105440 fix), so CI kept hitting an already-fixed bug. See #7257 for the full investigation.The same silent version-ordering hazard exists on every branch once a matching product repo publishes a higher-versioned microshift RPM. With repository priority 1 on the local repo, dnf prefers packages from it regardless of version ordering, so CI tests what it built.
How was this tested
bash -nandshellcheckon the modified script (no new findings). Behavioral verification comes from CI on this PR; not verified locally.This PR description was generated using AI. Please verify before acting on it.
Assisted-By: Claude Fable 5