Skip to content

Conversation

@jupierce
Copy link
Contributor

OpenShift and RHEL have come to an agreement whereby OCP will be able to release the RHEL kernel before the normal 6 week cadence of RHEL.
https://issues.redhat.com/browse/RHELPLAN-144928 tracks this agreement.
https://issues.redhat.com/browse/ART-5663 discussed ART/RHCOS agreement on how this would be handled at the pipeline level. The decision was to remove the constraint requiring the kernel to be source from baseos exclusively. By doing so, it ART has a more recent kernel build in its repository, it will be preferred.

OpenShift and RHEL have come to an agreement whereby OCP
will be able to release the RHEL kernel before the normal
6 week cadence of RHEL.
https://issues.redhat.com/browse/RHELPLAN-144928 tracks
this agreement.
https://issues.redhat.com/browse/ART-5663 discussed ART/RHCOS
agreement on how this would be handled at the pipeline level.
The decision was to remove the constraint requiring the kernel
to be source from baseos exclusively. By doing so, it ART
has a more recent kernel build in its repository, it will be
preferred.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jupierce
Once this PR has been reviewed and has the lgtm label, please assign cgwalters for approval by writing /assign @cgwalters in a comment. For more information see the Kubernetes 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

@jupierce
Copy link
Contributor Author

/cherrypick release-4.13

@openshift-cherrypick-robot

@jupierce: once the present PR merges, I will cherry-pick it on top of release-4.13 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.13

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/test-infra repository.

@jupierce
Copy link
Contributor Author

/cherrypick release-4.12

@openshift-cherrypick-robot

@jupierce: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

Details

In response to this:

/cherrypick release-4.12

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/test-infra repository.

@jlebon
Copy link
Member

jlebon commented Jan 30, 2023

I think we need to also update manifest-rhel-9.0.yaml and manifest-c9s.yaml to match. If this merges first, we'll have to make sure to update #1127 too before merging.

@cgwalters
Copy link
Member

Offhand I'm thinking this should merge into 4.12 directly; for 4.13 we're aiming at RHEL9 and I don't think this kernel flow has been looked at in that context at all, right? We're just going to ship the C9S kernel for now AFAIK, right?

@travier
Copy link
Member

travier commented Jan 30, 2023

Agree with Colin that this should go to 4.12 directly has this does not make much sense for 4.13 right now.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2023

@jupierce: 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/test-infra repository. I understand the commands that are listed here.

@travier
Copy link
Member

travier commented Jan 30, 2023

Closing as this has been moved to #1131
/close

@openshift-ci openshift-ci bot closed this Jan 30, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2023

@travier: Closed this PR.

Details

In response to this:

Closing as this has been moved to #1131
/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants