Skip to content

NO-ISSUE: fix mirror2 baseurls in ocp-5.0-rhel102.repo#79351

Merged
openshift-merge-bot[bot] merged 4 commits into
openshift:mainfrom
ashwindasr:fix-rhel102-repo-urls
May 15, 2026
Merged

NO-ISSUE: fix mirror2 baseurls in ocp-5.0-rhel102.repo#79351
openshift-merge-bot[bot] merged 4 commits into
openshift:mainfrom
ashwindasr:fix-rhel102-repo-urls

Conversation

@ashwindasr
Copy link
Copy Markdown
Contributor

@ashwindasr ashwindasr commented May 15, 2026

Summary

  • Fixed incorrect mirror2 baseurl paths in core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • URLs used wrong format rhel-10.2-*-rpms instead of rhel-102-* (matching the existing 4.21/4.22 configs)
  • Affected repos: baseos, appstream, nfv, highavailability, server-ose

Test plan

  • Verify mirror2 URLs resolve correctly (e.g. https://mirror2.openshift.com/enterprise/reposync/5.0/rhel-102-baseos/repodata/)
  • Compare with working 4.21/4.22 rhel102 repo configs for consistency

🤖 Generated with Claude Code

Summary

This PR fixes incorrect mirror2 baseurl paths in the OpenShift 5.0 RHEL 10.2 repository configuration used by CI to fetch packages.

What changed

Edited core-services/release-controller/_repos/ocp-5.0-rhel102.repo to correct mirror2 baseurl paths:

The rhel-10.2-server-ose-5.0 section points to the enterprise server OSE path (rhel-10-server-ose-rpms) as expected. Other repo settings were unchanged.

Impact

CI jobs and release tooling that rely on these mirror2 URLs for OCP 5.0 / RHEL 10.2 will now resolve and access the correct package repositories. This aligns the 5.0 rhel102 repo layout with the working conventions used for OCP 4.21/4.22, preventing package resolution failures during builds and tests.

The baseurls used incorrect path format (rhel-10.2-*-rpms) instead of
the correct format (rhel-102-*) matching the 4.21/4.22 repo configs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 15, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

Details

In response to this:

Summary

  • Fixed incorrect mirror2 baseurl paths in core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • URLs used wrong format rhel-10.2-*-rpms instead of rhel-102-* (matching the existing 4.21/4.22 configs)
  • Affected repos: baseos, appstream, nfv, highavailability, server-ose

Test plan

  • Verify mirror2 URLs resolve correctly (e.g. https://mirror2.openshift.com/enterprise/reposync/5.0/rhel-102-baseos/repodata/)
  • Compare with working 4.21/4.22 rhel102 repo configs for consistency

🤖 Generated with Claude Code

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-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 15, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 15, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 3622aa20-f8ce-4400-8d5b-97e01b6f521a

📥 Commits

Reviewing files that changed from the base of the PR and between 69bf3e2 and 39a212b.

📒 Files selected for processing (1)
  • core-services/release-controller/_repos/ocp-5.0-rhel102.repo

Walkthrough

This PR updates repository mirror URLs in the OCP 5.0 RHEL 10.2 configuration file. Six yum/dnf repository sections have their baseurl entries changed to point to new OpenShift mirror paths using rhel-102-* naming instead of the previous naming scheme.

Changes

Repository Mirror Configuration

Layer / File(s) Summary
Repository mirror URL updates
core-services/release-controller/_repos/ocp-5.0-rhel102.repo
Updated baseurl entries across six repository sections (rhel-10.2-baseos, rhel-10.2-appstream, rhel-10.2-nfv, rhel-10.2-highavailability, rhel-10.2-server-ose-5.0, rhel-10.2-early-kernel) to reference new OpenShift mirror paths with rhel-102-* or rhel-10-server-ose-rpms naming.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

lgtm, approved

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly describes the main change: fixing mirror2 baseurls in a specific repository file, which matches the primary objective of correcting baseurl paths.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed This PR modifies only a yum/dnf repository configuration file with baseurl updates. No Ginkgo tests or test files are included. The check for stable test names is not applicable.
Test Structure And Quality ✅ Passed Not applicable: The PR only modifies repository configuration file (ocp-5.0-rhel102.repo), not Ginkgo test code. The custom check for test structure and quality does not apply to this change.
Microshift Test Compatibility ✅ Passed This PR only modifies a repository configuration file (ocp-5.0-rhel102.repo) and does not add any Ginkgo e2e tests. The MicroShift Test Compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR only modifies a yum repository configuration file with no Go test code or Ginkgo e2e tests added. The SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed PR modifies only a YUM/DNF repository configuration file (ocp-5.0-rhel102.repo), not deployment manifests, operator code, or controllers. No Kubernetes scheduling constraints are introduced.
Ote Binary Stdout Contract ✅ Passed PR modifies only a repository configuration file with mirror URLs. No code or test infrastructure changes present. OTE Stdout check does not apply.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR does not add any Ginkgo e2e tests. Changes are limited to .repo configuration files. The custom check is only applicable to PRs adding new e2e tests.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from jmguzik and psalajova May 15, 2026 17:44
ashwindasr and others added 2 commits May 15, 2026 13:45
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@core-services/release-controller/_repos/ocp-5.0-rhel102.repo`:
- Line 3: The repo file change at baseurl =
https://mirror2.openshift.com/enterprise/reposync/5.0/rhel-102-baseos/ needs
validation with the repo-file validator; run /test-repo-files (or the CI job
that runs it) against
core-services/release-controller/_repos/ocp-5.0-rhel102.repo and the other
affected ocp-*.repo edits (lines referenced: 3, 14, 25, 36, 58, 70), capture and
attach the full validator output or CI job link to the PR, and if the validator
reports issues, correct the baseurl/CDN patterns accordingly and re-run until it
passes before merging.
- Line 58: The early-kernel repository's baseurl is incorrect: update the
baseurl value used in the early-kernel repo block (the line currently
referencing rhel-10-server-ose-rpms) to use the rhel-102-early-kernel path;
specifically replace the existing baseurl string with
https://mirror2.openshift.com/enterprise/reposync/5.0/rhel-102-early-kernel/ so
the early-kernel repo matches the 4.21/4.22 pattern.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 51046597-791d-4109-ac78-f3c853fd61c3

📥 Commits

Reviewing files that changed from the base of the PR and between a28f9e7 and 69bf3e2.

📒 Files selected for processing (1)
  • core-services/release-controller/_repos/ocp-5.0-rhel102.repo

Comment thread core-services/release-controller/_repos/ocp-5.0-rhel102.repo
Comment thread core-services/release-controller/_repos/ocp-5.0-rhel102.repo
Matches the 4.21/4.22 pattern instead of incorrectly reusing
the rhel-10-server-ose-rpms path.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@ashwindasr: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Copy link
Copy Markdown
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

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 15, 2026
@dustymabe
Copy link
Copy Markdown
Member

/assign @joepvd

@jupierce
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ashwindasr, dustymabe, jupierce

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 May 15, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

@ashwindasr: 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.

@openshift-merge-bot openshift-merge-bot Bot merged commit 92ea121 into openshift:main May 15, 2026
6 checks passed
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

@ashwindasr: Updated the following 15 configmaps:

  • base-repos configmap in namespace ocp at cluster build06 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build01 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster vsphere02 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build11 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build03 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build09 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster core-ci using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster app.ci using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build04 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build10 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build07 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build08 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build02 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build05 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • base-repos configmap in namespace ocp at cluster build12 using the following files:
    • key ocp-5.0-rhel102.repo using file core-services/release-controller/_repos/ocp-5.0-rhel102.repo
Details

In response to this:

Summary

  • Fixed incorrect mirror2 baseurl paths in core-services/release-controller/_repos/ocp-5.0-rhel102.repo
  • URLs used wrong format rhel-10.2-*-rpms instead of rhel-102-* (matching the existing 4.21/4.22 configs)
  • Affected repos: baseos, appstream, nfv, highavailability, server-ose

Test plan

  • Verify mirror2 URLs resolve correctly (e.g. https://mirror2.openshift.com/enterprise/reposync/5.0/rhel-102-baseos/repodata/)
  • Compare with working 4.21/4.22 rhel102 repo configs for consistency

🤖 Generated with Claude Code

Summary

This PR fixes incorrect mirror2 baseurl paths in the OpenShift 5.0 RHEL 10.2 repository configuration used by CI to fetch packages.

What changed

Edited core-services/release-controller/_repos/ocp-5.0-rhel102.repo to correct mirror2 baseurl paths:

The rhel-10.2-server-ose-5.0 section points to the enterprise server OSE path (rhel-10-server-ose-rpms) as expected. Other repo settings were unchanged.

Impact

CI jobs and release tooling that rely on these mirror2 URLs for OCP 5.0 / RHEL 10.2 will now resolve and access the correct package repositories. This aligns the 5.0 rhel102 repo layout with the working conventions used for OCP 4.21/4.22, preventing package resolution failures during builds and tests.

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

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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants