release-controller: migrate ocp-5.1-rhel9.repo external repos from reposync to CDN

[redhat-chai-bot]

Summary

The 5.1 branching automation (PR #83050) generated ocp-5.1-rhel9.repo with reposync S3 mirror URLs for external RHEL repos (baseos, appstream, nfv, highavailability, codeready-builder). But reposync is intentionally disabled for 5.x external repos, so the S3 mirror is empty, causing HTTP 404 errors in CI builds (e.g. ironic/baremetal builds failing on mtools-4.0.26-3.el9.x86_64.rpm).

PR #81054 previously migrated RHEL 10 and OpenStack repos from reposync to CDN, but the RHEL 9 repos were missed.

Changes

Migrate 14 external repo sections across all 4 architectures (x86_64, aarch64, ppc64le, s390x) from reposync to CDN:

• baseos (4 arches) — cdn.redhat.com/content/e4s/rhel9/9.8/{arch}/baseos/os/
• appstream (4 arches) — cdn.redhat.com/content/e4s/rhel9/9.8/{arch}/appstream/os/
• nfv (x86_64 only) — cdn.redhat.com/content/e4s/rhel9/9.8/x86_64/nfv/os/
• highavailability (x86_64 only) — cdn.redhat.com/content/e4s/rhel9/9.8/x86_64/highavailability/os/
• codeready-builder (4 arches) — cdn.redhat.com/content/eus/rhel9/9.8/{arch}/codeready-builder/os/

Auth is changed from basic auth (username_file/password_file) to SSL client cert (sslclientkey/sslclientcert), matching ocp-5.0-rhel9.repo.

ART plashet repos (server-ose, early-kernel) remain on reposync as intended. fast-datapath repos were already on CDN and are unchanged.

---

AI-generated. Review for accuracy.

@locriandev requested via Chai Bot

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@redhat-chai-bot: 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.

[elfosardo]

/lgtm

[joepvd]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo, joepvd, redhat-chai-bot

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:

• core-services/release-controller/OWNERS [joepvd]

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

[openshift-ci]

@redhat-chai-bot: 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-ci]

@redhat-chai-bot: Updated the following 16 configmaps:

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

Details

In response to this:

Summary

The 5.1 branching automation (PR #83050) generated ocp-5.1-rhel9.repo with reposync S3 mirror URLs for external RHEL repos (baseos, appstream, nfv, highavailability, codeready-builder). But reposync is intentionally disabled for 5.x external repos, so the S3 mirror is empty, causing HTTP 404 errors in CI builds (e.g. ironic/baremetal builds failing on mtools-4.0.26-3.el9.x86_64.rpm).

PR #81054 previously migrated RHEL 10 and OpenStack repos from reposync to CDN, but the RHEL 9 repos were missed.

Changes

Migrate 14 external repo sections across all 4 architectures (x86_64, aarch64, ppc64le, s390x) from reposync to CDN:

• baseos (4 arches) — cdn.redhat.com/content/e4s/rhel9/9.8/{arch}/baseos/os/
• appstream (4 arches) — cdn.redhat.com/content/e4s/rhel9/9.8/{arch}/appstream/os/
• nfv (x86_64 only) — cdn.redhat.com/content/e4s/rhel9/9.8/x86_64/nfv/os/
• highavailability (x86_64 only) — cdn.redhat.com/content/e4s/rhel9/9.8/x86_64/highavailability/os/
• codeready-builder (4 arches) — cdn.redhat.com/content/eus/rhel9/9.8/{arch}/codeready-builder/os/

Auth is changed from basic auth (username_file/password_file) to SSL client cert (sslclientkey/sslclientcert), matching ocp-5.0-rhel9.repo.

ART plashet repos (server-ose, early-kernel) remain on reposync as intended. fast-datapath repos were already on CDN and are unchanged.

---

AI-generated. Review for accuracy.

@locriandev requested via Chai Bot

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.