Skip to content

COS-3946: Backport rhel-10.2 support to release-4.21 branch#1898

Merged
sdodson merged 4 commits intoopenshift:release-4.21from
prestist:release-4.21
Mar 9, 2026
Merged

COS-3946: Backport rhel-10.2 support to release-4.21 branch#1898
sdodson merged 4 commits intoopenshift:release-4.21from
prestist:release-4.21

Conversation

@prestist
Copy link
Copy Markdown
Contributor

@prestist prestist commented Feb 18, 2026

Backport rhel-10.2 support to release-4.21 branch from master (PR #1892) and enable rhel-10.2 plashets.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 18, 2026
@prestist prestist changed the title rhel-10.1: enable rhel-10.1 plashets Backport rhel-10.2 support to release-4.21 branch Feb 18, 2026
Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
 - Let's sync the CI with what we have also in
   rhel-coreos-config, doing it for both RHEL 9/10

Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
@dustymabe
Copy link
Copy Markdown
Member

probably also need to backport 2ba2ed9

@prestist
Copy link
Copy Markdown
Contributor Author

Once we merge #1899 I will backport it here as well.

Ok I will include that.

 - Fix wrong versions of repos under rhel-10.2

Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
Copy link
Copy Markdown
Contributor

@marmijo marmijo 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 Feb 19, 2026
@cverna cverna changed the title Backport rhel-10.2 support to release-4.21 branch COS-3946: Backport rhel-10.2 support to release-4.21 branch Feb 23, 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 Feb 23, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 23, 2026

@prestist: This pull request references COS-3946 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 sub-task to target the "4.21.z" version, but no target version was set.

Details

In response to this:

Backport rhel-10.2 support to release-4.21 branch from master (PR #1892) and enable rhel-10.2 plashets.

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.

@cverna
Copy link
Copy Markdown
Contributor

cverna commented Feb 23, 2026

/label backport-risk-assessed

@cverna
Copy link
Copy Markdown
Contributor

cverna commented Feb 23, 2026

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 23, 2026

@cverna: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-release-oversight, openshift-staff-engineers, openshift-sustaining-engineers

Details

In response to this:

/label backport-risk-assessed

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.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 24, 2026
@prestist
Copy link
Copy Markdown
Contributor Author

Ok, brought in the change that landed in master now as well.

Comment thread ci/get-ocp-repo.sh Outdated
rm -f "$dest"
for url in "${urls[@]}"; do
curl --fail -L "$url" >> "$dest"
curl --fail -L "$url" >> "$dest" || echo "Warning: Failed to fetch $url" >&2
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.

I'm concerned this change might obscure infra issues with RHEL 9.6 repos. We'd want the script to fail fast if those repos are unavailable for any reason.

Are we also hitting this issue on the master branch and does this need to be changed there too?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 let's keep it sync with master

@ravanelli
Copy link
Copy Markdown
Member

It depends on openshift/release#75822

@ravanelli
Copy link
Copy Markdown
Member

/retest-required

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 9, 2026

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

Copy link
Copy Markdown
Member

@ravanelli ravanelli 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 Mar 9, 2026
@ravanelli
Copy link
Copy Markdown
Member

/backport-risk-assessed

@ravanelli
Copy link
Copy Markdown
Member

/jira/valid-bug
/verified

@openshift-ci-robot
Copy link
Copy Markdown

@ravanelli: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/jira/valid-bug
/verified

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.

@ravanelli
Copy link
Copy Markdown
Member

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 9, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@ravanelli: The verified label has been added.

Details

In response to this:

/verified bypass

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

openshift-ci bot commented Mar 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marmijo, prestist, ravanelli

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:
  • OWNERS [marmijo,prestist,ravanelli]

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

@sdodson sdodson merged commit 00961b9 into openshift:release-4.21 Mar 9, 2026
2 of 3 checks passed
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants