Skip to content

fix rhel9 repo names for 4.22 and 5.0#78086

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
fgallott:fix-ci-reponames
Apr 21, 2026
Merged

fix rhel9 repo names for 4.22 and 5.0#78086
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
fgallott:fix-ci-reponames

Conversation

@fgallott
Copy link
Copy Markdown
Contributor

@fgallott fgallott commented Apr 21, 2026

follows #77982

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED

Summary by CodeRabbit

  • Chores
    • Updated repository configuration identifiers across all supported architectures (x86_64, ppc64le, s390x, and aarch64) to use general RHEL 9 versioning. All repository access points, enabled settings, authentication mechanisms, and other configuration details remain unchanged. This is a maintenance update with no direct impact to system functionality or user operations.

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 21, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ba2b3e47-209b-489d-86a8-8cb066800373

📥 Commits

Reviewing files that changed from the base of the PR and between b841161 and f00139a.

📒 Files selected for processing (2)
  • core-services/release-controller/_repos/ocp-4.22-rhel9.repo
  • core-services/release-controller/_repos/ocp-5.0-rhel9.repo

Walkthrough

Repository section identifiers and corresponding name fields in two RHEL9 repository configuration files were updated from minor-version-qualified names (e.g., rhel-9.8-baseos) to general RHEL 9-qualified names (e.g., rhel-9-baseos) across multiple architectures. Configuration settings remain unchanged.

Changes

Cohort / File(s) Summary
Repository Configuration Updates
core-services/release-controller/_repos/ocp-4.22-rhel9.repo, core-services/release-controller/_repos/ocp-5.0-rhel9.repo
Renamed repository section identifiers and name fields from RHEL minor-version formats (rhel-9.8-*, rhel-98-*) to general RHEL 9 formats (rhel-9-*) across x86_64, ppc64le, s390x, and aarch64 architectures. Server OSE section names also simplified by removing OCP version suffixes. All other repository configuration settings preserved.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 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 'fix rhel9 repo names for 4.22 and 5.0' accurately and clearly describes the main change: updating RHEL 9 repository names in configuration files for OCP versions 4.22 and 5.0.
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 PR contains only YUM repository configuration file changes, no Ginkgo test modifications.
Test Structure And Quality ✅ Passed PR modifies only repository configuration files (.repo files) for yum/dnf package management, not test code or Ginkgo tests.
Microshift Test Compatibility ✅ Passed This pull request does not add any new Ginkgo e2e tests. The changes are exclusively to RHEL YUM/DNF repository configuration files where repository section identifiers are being renamed from minor-version-qualified variants to general RHEL 9-qualified variants. Since no e2e tests are being introduced or modified, the MicroShift test compatibility check does not apply to this pull request.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR only modifies YUM/DNF repository configuration files, with no Ginkgo e2e tests added or modified, making the SNO compatibility check not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Modified files are YUM/DNF repository configuration files (.repo) containing package repository definitions, not deployment manifests, operator code, or controllers. No scheduling constraints or topology-related configurations present.
Ote Binary Stdout Contract ✅ Passed This PR modifies only YUM/DNF repository configuration files (.repo files) containing repository metadata, which are plaintext configuration files with no executable code or stdout operations.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This pull request only modifies YUM/DNF repository configuration files, not Ginkgo e2e test code.

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

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

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

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

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 21, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@fgallott: 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.

@fgallott
Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 21, 2026
Copy link
Copy Markdown
Contributor

@joepvd joepvd 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 Apr 21, 2026
@joepvd
Copy link
Copy Markdown
Contributor

joepvd commented Apr 21, 2026

/unhold

@openshift-ci openshift-ci Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Apr 21, 2026
@joepvd
Copy link
Copy Markdown
Contributor

joepvd commented Apr 21, 2026

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 21, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fgallott, joepvd

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

openshift-ci Bot commented Apr 21, 2026

@fgallott: 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 987c890 into openshift:main Apr 21, 2026
6 checks passed
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 21, 2026

@fgallott: Updated the following 14 configmaps:

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

In response to this:

follows #77982

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED

Summary by CodeRabbit

  • Chores
  • Updated repository configuration identifiers across all supported architectures (x86_64, ppc64le, s390x, and aarch64) to use general RHEL 9 versioning. All repository access points, enabled settings, authentication mechanisms, and other configuration details remain unchanged. This is a maintenance update with no direct impact to system functionality or user operations.

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.

@fgallott fgallott deleted the fix-ci-reponames branch April 21, 2026 09:11
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. 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.

2 participants