Skip to content

COS-3900: Start using rhel-10.2 #1892

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-bot merged 2 commits into from
Feb 9, 2026
Merged

COS-3900: Start using rhel-10.2 #1892

openshift-merge-bot merged 2 commits into from
Feb 9, 2026
+17 −16

Conversation

@ravanelli
Copy link
Member

@ravanelli ravanelli commented Jan 29, 2026

No description provided.

@openshift-ci openshift-ci bot requested review from HuijingHei and tlbueno January 29, 2026 18:31
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 29, 2026
tlbueno
tlbueno approved these changes Jan 29, 2026
View reviewed changes
Copy link
Member

@tlbueno tlbueno left a comment

Choose a reason for hiding this comment

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

lgtm

travier
travier reviewed Feb 2, 2026
View reviewed changes
@ravanelli
Start using rhel-10.2
93c21cb 
Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
@dustymabe
Copy link
Member

dustymabe commented Feb 2, 2026

/lgtm

@dustymabe dustymabe changed the title Start using rhel-10.2 COS-3900: Start using rhel-10.2 Feb 2, 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 2, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 2, 2026 •
edited by openshift-ci bot
Loading

@ravanelli: This pull request references COS-3900 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 "4.22.0" version, but no target version was set.

Details

In response to this:

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 added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2026
@ravanelli
Copy link
Member Author

ravanelli commented Feb 2, 2026

/retest-required

1 similar comment
@ravanelli
Copy link
Member Author

ravanelli commented Feb 3, 2026

/retest-required

@dustymabe
Copy link
Member

dustymabe commented Feb 3, 2026

/retest

1 similar comment
@ravanelli
Copy link
Member Author

ravanelli commented Feb 4, 2026

/retest

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2026
@ravanelli
ci: Start using rhel-10.2 for CI as well
c5a7017 
 - 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>
@ravanelli
Copy link
Member Author

ravanelli commented Feb 4, 2026

We need a new build of rhel-9.8 to update the Kernel with the new versions on the repos, it is running now

@ravanelli
Copy link
Member Author

ravanelli commented Feb 9, 2026

/retest-required

3 similar comments
@ravanelli
Copy link
Member Author

ravanelli commented Feb 9, 2026

/retest-required

@ravanelli
Copy link
Member Author

ravanelli commented Feb 9, 2026

/retest-required

@ravanelli
Copy link
Member Author

ravanelli commented Feb 9, 2026

/retest-required

@ravanelli
Copy link
Member Author

ravanelli commented Feb 9, 2026

The CI got update to 9.8.20260207-0 to not to 9.8.20260208-0 yet.
The rhel-coreo-base is already in 9.8.20260208-0. It may not being forcing a pull, let's wait more.

@ravanelli
Copy link
Member Author

ravanelli commented Feb 9, 2026

/test images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2026

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

@dustymabe
Copy link
Member

dustymabe commented Feb 9, 2026

/lgtm
/verified by ci/prow/images

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

openshift-ci-robot commented Feb 9, 2026

@dustymabe: This PR has been marked as verified by ci/prow/images.

Details

In response to this:

/lgtm
/verified by ci/prow/images

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 added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustymabe, ravanelli, tlbueno

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 [dustymabe,ravanelli,tlbueno]

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

@openshift-merge-bot openshift-merge-bot bot merged commit 76d7bb2 into openshift:master Feb 9, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@travier travier travier left review comments

@HuijingHei HuijingHei Awaiting requested review from HuijingHei

+1 more reviewer

@tlbueno tlbueno tlbueno approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@dustymabe dustymabe

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@ravanelli @dustymabe @openshift-ci-robot @tlbueno @travier