Skip to content

ART-19228: Disable reposync for RHEL 10.2 GA repos (openshift-5.0) - #10805

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift-eng:openshift-5.0from
locriandev:disable-rhel102-reposync
May 27, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift-eng:openshift-5.0from
locriandev:disable-rhel102-reposync

Conversation

@locriandev

Copy link
Copy Markdown
Contributor

Summary

RHEL 10.2 has gone GA and is available via E4S. This PR disables reposync for RHEL 10.2 repos to use E4S content directly instead of syncing to S3 mirrors.

Changes

Disabled reposync for the following repos:

  • rhel-102-appstream
  • rhel-102-baseos
  • rhel-102-highavailability
  • rhel-102-nfv (also updated baseurl from nightly composes to E4S)

Unchanged

  • rhel-102-fast-datapath: Not available in E4S
  • rhel-102-early-kernel: Uses plashet source, not E4S

Benefits

  • No sync lag - direct access to GA content
  • Cost savings - no S3 storage/bandwidth for RHEL 10.2 content
  • Eliminates version mismatches (e.g., openssl-3.5.5-1 vs 3.5.5-2)

Related PRs

  • openshift/release PR to update repo files to use E4S URLs directly
  • Similar changes for openshift-4.22 and openshift-4.23 branches

Issue

Resolves package version mismatches where reposync was syncing newer package versions while CI jobs were looking for older versions that no longer exist in the GA repo.

Related Slack thread: https://redhat-internal.slack.com/archives/CBN38N3MW/p1779418280741809

RHEL 10.2 has gone GA and is available via E4S. Disable reposync for
the following repos to use E4S content directly instead of syncing to
S3 mirrors:

- rhel-102-appstream
- rhel-102-baseos
- rhel-102-highavailability
- rhel-102-nfv (also updated baseurl from nightly composes to E4S)

This resolves package version mismatches where reposync was syncing
newer package versions (e.g., openssl-3.5.5-2) while CI jobs were
looking for older versions (e.g., openssl-3.5.5-1) that no longer
exist in the GA repo.

rhel-102-fast-datapath and rhel-102-early-kernel are unchanged:
- fast-datapath: not available in E4S
- early-kernel: uses plashet source, not E4S

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

rh-pre-commit.version: 2.4.0
rh-pre-commit.check-secrets: ENABLED
@locriandev locriandev changed the title Disable reposync for RHEL 10.2 GA repos (openshift-5.0) ART-19228: Disable reposync for RHEL 10.2 GA repos (openshift-5.0) May 27, 2026
@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 27, 2026
@openshift-ci-robot

openshift-ci-robot commented May 27, 2026

Copy link
Copy Markdown

@locriandev: This pull request references ART-19228 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

RHEL 10.2 has gone GA and is available via E4S. This PR disables reposync for RHEL 10.2 repos to use E4S content directly instead of syncing to S3 mirrors.

Changes

Disabled reposync for the following repos:

  • rhel-102-appstream
  • rhel-102-baseos
  • rhel-102-highavailability
  • rhel-102-nfv (also updated baseurl from nightly composes to E4S)

Unchanged

  • rhel-102-fast-datapath: Not available in E4S
  • rhel-102-early-kernel: Uses plashet source, not E4S

Benefits

  • No sync lag - direct access to GA content
  • Cost savings - no S3 storage/bandwidth for RHEL 10.2 content
  • Eliminates version mismatches (e.g., openssl-3.5.5-1 vs 3.5.5-2)

Related PRs

  • openshift/release PR to update repo files to use E4S URLs directly
  • Similar changes for openshift-4.22 and openshift-4.23 branches

Issue

Resolves package version mismatches where reposync was syncing newer package versions while CI jobs were looking for older versions that no longer exist in the GA repo.

Related Slack thread: https://redhat-internal.slack.com/archives/CBN38N3MW/p1779418280741809

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.

@joepvd joepvd left a comment

Copy link
Copy Markdown
Contributor

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 27, 2026
@openshift-ci

openshift-ci Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 27, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 1115226 into openshift-eng:openshift-5.0 May 27, 2026
3 checks passed
@locriandev
locriandev deleted the disable-rhel102-reposync branch May 28, 2026 09:51
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants