Skip to content

OKD-387: Switch to released (mirror) repos for SCOS builds#1947

Open
pskrbasu wants to merge 1 commit into
openshift:release-4.22from
pskrbasu:fix-c10s-compose-to-mirror-4.22
Open

OKD-387: Switch to released (mirror) repos for SCOS builds#1947
pskrbasu wants to merge 1 commit into
openshift:release-4.22from
pskrbasu:fix-c10s-compose-to-mirror-4.22

Conversation

@pskrbasu

Copy link
Copy Markdown

Summary

  • Cherry-pick of 64af4d8 to release-4.22
  • Switches c10s.repo URLs from composes.stream.centos.org to mirror.stream.centos.org
  • Removes c10s-mirror.repo (no longer needed since c10s.repo now uses the mirror URLs directly)

The compose repos only carry the latest version of each package, which causes version conflicts (e.g. openssl-libs, NetworkManager) when the base SCOS image was built against older versions that get filtered out. The mirror repos carry multiple versions, allowing dnf to resolve compatible package sets.

This is needed for the SCOS 4.22 CI config fix in openshift/release#81863.

This is the openshift/os equivalent of [1] against rhel-coreos-config
where we made the mirror repos the only ones we have defined to simplify
versioning conflicts we have sometimes.

[1] coreos/rhel-coreos-config@718d19e
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 15, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 15, 2026

Copy link
Copy Markdown

@pskrbasu: This pull request references OKD-387 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

  • Cherry-pick of 64af4d8 to release-4.22
  • Switches c10s.repo URLs from composes.stream.centos.org to mirror.stream.centos.org
  • Removes c10s-mirror.repo (no longer needed since c10s.repo now uses the mirror URLs directly)

The compose repos only carry the latest version of each package, which causes version conflicts (e.g. openssl-libs, NetworkManager) when the base SCOS image was built against older versions that get filtered out. The mirror repos carry multiple versions, allowing dnf to resolve compatible package sets.

This is needed for the SCOS 4.22 CI config fix in openshift/release#81863.

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-ci
openshift-ci Bot requested review from ravanelli and travier July 15, 2026 03:40
@openshift-ci

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

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

@ausil

ausil commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2026
@openshift-ci

openshift-ci Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ausil, pskrbasu
Once this PR has been reviewed and has the lgtm label, please assign travier for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@Prashanth684

Copy link
Copy Markdown
Contributor

/cc @dustymabe

@openshift-ci
openshift-ci Bot requested a review from dustymabe July 16, 2026 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants