Skip to content

Remove rhel-9-openstack-17-rpms from base rhel9 repo files#76590

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
elfosardo:remove-openstack-from-base-rhel9
Mar 27, 2026
Merged

Remove rhel-9-openstack-17-rpms from base rhel9 repo files#76590
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
elfosardo:remove-openstack-from-base-rhel9

Conversation

@elfosardo
Copy link
Copy Markdown
Contributor

@elfosardo elfosardo commented Mar 20, 2026

The rhel-9-openstack-17-rpms repository was included in the base
ocp-*-rhel9.repo files, making OpenStack 17 packages available to
all rhel9-based image builds. This is unnecessary for most images
and should be opt-in, similar to how ironic repos are handled.

The packages in the OpenStack 17 repo are old and outdated at this
point, so having them enabled by default for every rhel9 image
build adds unnecessary exposure to stale dependencies without any
benefit to the vast majority of images.

The separate ocp-*-openstack.repo files already exist for all
affected versions (4.16-4.23, 5.0) and are served by their own
content-mirror services (base-openstack-4-Y.ocp.svc).

Images that need OpenStack 17 packages should use a
pipeline_image_cache_step to inject the openstack repo, following
the same pattern used by ironic-image. For example, in a
ci-operator config for OCP 4.22:

raw_steps:

Then use "tools-openstack" as the "from:" in your image build
definition instead of "tools".

The openshift/origin CI configs are updated here as an example of
this pattern, since the origin tests image is the only known
consumer of the openstack repo in the production pipeline.

See ci-operator/config/openshift/ironic-image/ for another working
example of this pattern with the ironic repos.

@openshift-ci openshift-ci bot requested review from droslean and psalajova March 20, 2026 10:42
@elfosardo
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 Mar 20, 2026
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Mar 20, 2026
@elfosardo elfosardo force-pushed the remove-openstack-from-base-rhel9 branch from a5973b7 to ecac380 Compare March 20, 2026 10:48
@elfosardo
Copy link
Copy Markdown
Contributor Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 20, 2026
@openshift-ci-robot openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Mar 20, 2026
@elfosardo
Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-origin-release-4.18-images pull-ci-openshift-origin-release-4.19-images pull-ci-openshift-origin-release-5.0-images pull-ci-openshift-origin-release-4.23-images pull-ci-openshift-origin-release-4.22-images pull-ci-openshift-origin-release-4.21-images pull-ci-openshift-origin-release-4.16-images pull-ci-openshift-origin-main-images pull-ci-openshift-origin-release-4.20-images pull-ci-openshift-origin-release-4.17-images

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@elfosardo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

The rhel-9-openstack-17-rpms repository was included in the base
ocp-*-rhel9.repo files, making OpenStack 17 packages available to
all rhel9-based image builds. This is unnecessary for most images
and should be opt-in, similar to how ironic repos are handled.

The packages in the OpenStack 17 repo are old and outdated at this
point, so having them enabled by default for every rhel9 image
build adds unnecessary exposure to stale dependencies without any
benefit to the vast majority of images.

The separate ocp-*-openstack.repo files already exist for all
affected versions (4.16-4.23, 5.0) and are served by their own
content-mirror services (base-openstack-4-Y.ocp.svc).

Images that need OpenStack 17 packages should use a
pipeline_image_cache_step to inject the openstack repo, following
the same pattern used by ironic-image. For example, in a
ci-operator config for OCP 4.22:

  raw_steps:
  - pipeline_image_cache_step:
      commands: |
        curl http://base-openstack-4-22.ocp.svc > /etc/yum.repos.art/ci/base-openstack-4-22.repo
      from: tools
      to: tools-openstack

Then use "tools-openstack" as the "from:" in your image build
definition instead of "tools".

The openshift/origin CI configs are updated here as an example of
this pattern, since the origin tests image is the only known
consumer of the openstack repo in the production pipeline.

See ci-operator/config/openshift/ironic-image/ for another working
example of this pattern with the ironic repos.
@elfosardo elfosardo force-pushed the remove-openstack-from-base-rhel9 branch from ecac380 to 12bbb57 Compare March 20, 2026 11:56
@elfosardo
Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-origin-release-4.18-images pull-ci-openshift-origin-release-4.19-images pull-ci-openshift-origin-release-5.0-images pull-ci-openshift-origin-release-4.23-images pull-ci-openshift-origin-release-4.22-images pull-ci-openshift-origin-release-4.21-images pull-ci-openshift-origin-release-4.16-images pull-ci-openshift-origin-main-images pull-ci-openshift-origin-release-4.20-images pull-ci-openshift-origin-release-4.17-images

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@elfosardo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@elfosardo: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-origin-release-4.23-e2e-agnostic-ovn-cmd openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-csi openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-disruptive openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-etcd-certrotation openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-etcd-recovery openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-jenkins openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-cgroupsv2 openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-edge-zones openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-etcd-scaling openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-fips openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-image-registry openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-kube-apiserver-rollout openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-kubevirt openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-microshift openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-microshift-serial openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-serial-1of2 openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-serial-2of2 openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-serial-fast openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-serial-ipsec openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-serial-publicnet-1of2 openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-serial-publicnet-2of2 openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-single-node openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-single-node-serial openshift/origin presubmit Ci-operator config changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-single-node-techpreview openshift/origin presubmit Ci-operator config changed

A total of 764 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

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.

@joepvd
Copy link
Copy Markdown
Contributor

joepvd commented Mar 20, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2026
@elfosardo
Copy link
Copy Markdown
Contributor Author

@elfosardo
Copy link
Copy Markdown
Contributor Author

@bertinatto @sosiouxme @dgoodwin @deads2k can you please have a look ?
this is an important fix to properly test the Metal Platform containers (and honestly, all other containers....)

@elfosardo
Copy link
Copy Markdown
Contributor Author

@openshift-ci openshift-ci bot requested a review from xueqzhan March 25, 2026 09:12
@elfosardo
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@elfosardo: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Mar 26, 2026
@petr-muller
Copy link
Copy Markdown
Member

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo, joepvd, petr-muller

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

openshift-ci bot commented Mar 27, 2026

@elfosardo: 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 9cb44de into openshift:main Mar 27, 2026
23 checks passed
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 27, 2026

@elfosardo: Updated the following 14 configmaps:

  • base-repos configmap in namespace ocp at cluster build05 using the following files:
    • key ocp-4.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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 build10 using the following files:
    • key ocp-4.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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.16-rhel9.repo using file core-services/release-controller/_repos/ocp-4.16-rhel9.repo
    • key ocp-4.17-rhel9.repo using file core-services/release-controller/_repos/ocp-4.17-rhel9.repo
    • key ocp-4.18-rhel9.repo using file core-services/release-controller/_repos/ocp-4.18-rhel9.repo
    • key ocp-4.19-rhel9.repo using file core-services/release-controller/_repos/ocp-4.19-rhel9.repo
    • key ocp-4.20-rhel9.repo using file core-services/release-controller/_repos/ocp-4.20-rhel9.repo
    • key ocp-4.21-rhel9.repo using file core-services/release-controller/_repos/ocp-4.21-rhel9.repo
    • key ocp-4.22-rhel9.repo using file core-services/release-controller/_repos/ocp-4.22-rhel9.repo
    • key ocp-4.23-rhel9.repo using file core-services/release-controller/_repos/ocp-4.23-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:

The rhel-9-openstack-17-rpms repository was included in the base
ocp-*-rhel9.repo files, making OpenStack 17 packages available to
all rhel9-based image builds. This is unnecessary for most images
and should be opt-in, similar to how ironic repos are handled.

The packages in the OpenStack 17 repo are old and outdated at this
point, so having them enabled by default for every rhel9 image
build adds unnecessary exposure to stale dependencies without any
benefit to the vast majority of images.

The separate ocp-*-openstack.repo files already exist for all
affected versions (4.16-4.23, 5.0) and are served by their own
content-mirror services (base-openstack-4-Y.ocp.svc).

Images that need OpenStack 17 packages should use a
pipeline_image_cache_step to inject the openstack repo, following
the same pattern used by ironic-image. For example, in a
ci-operator config for OCP 4.22:

raw_steps:

Then use "tools-openstack" as the "from:" in your image build
definition instead of "tools".

The openshift/origin CI configs are updated here as an example of
this pattern, since the origin tests image is the only known
consumer of the openstack repo in the production pipeline.

See ci-operator/config/openshift/ironic-image/ for another working
example of this pattern with the ironic repos.

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.

mgencur pushed a commit to mgencur/release that referenced this pull request Mar 30, 2026
…#76590)

The rhel-9-openstack-17-rpms repository was included in the base
ocp-*-rhel9.repo files, making OpenStack 17 packages available to
all rhel9-based image builds. This is unnecessary for most images
and should be opt-in, similar to how ironic repos are handled.

The packages in the OpenStack 17 repo are old and outdated at this
point, so having them enabled by default for every rhel9 image
build adds unnecessary exposure to stale dependencies without any
benefit to the vast majority of images.

The separate ocp-*-openstack.repo files already exist for all
affected versions (4.16-4.23, 5.0) and are served by their own
content-mirror services (base-openstack-4-Y.ocp.svc).

Images that need OpenStack 17 packages should use a
pipeline_image_cache_step to inject the openstack repo, following
the same pattern used by ironic-image. For example, in a
ci-operator config for OCP 4.22:

  raw_steps:
  - pipeline_image_cache_step:
      commands: |
        curl http://base-openstack-4-22.ocp.svc > /etc/yum.repos.art/ci/base-openstack-4-22.repo
      from: tools
      to: tools-openstack

Then use "tools-openstack" as the "from:" in your image build
definition instead of "tools".

The openshift/origin CI configs are updated here as an example of
this pattern, since the origin tests image is the only known
consumer of the openstack repo in the production pipeline.

See ci-operator/config/openshift/ironic-image/ for another working
example of this pattern with the ironic repos.
mandre added a commit to shiftstack/release that referenced this pull request Mar 31, 2026
After the openstack repos were removed from the base image via
openshift#76590...
mandre added a commit to shiftstack/release that referenced this pull request Mar 31, 2026
After the openstack repos were removed from the base image via
openshift#76590...
mandre added a commit to shiftstack/release that referenced this pull request Mar 31, 2026
After the openstack repos were removed from the base image via
openshift#76590...
openshift-merge-bot bot pushed a commit that referenced this pull request Mar 31, 2026
After the openstack repos were removed from the base image via
#76590...
HarshwardhanPatil07 pushed a commit to HarshwardhanPatil07/release that referenced this pull request Apr 2, 2026
After the openstack repos were removed from the base image via
openshift#76590...
acornett21 pushed a commit to acornett21/openshift-release that referenced this pull request Apr 3, 2026
After the openstack repos were removed from the base image via
openshift#76590...
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.

4 participants