NO-JIRA: manifest-rhel-9.6: add early kernel repo

[jlebon]

We need to enable the rhel-9.6-early-kernel repo to ensure that we still get access to the early kernels. Non-el-only variants (like ocp-rhel-9.6) get this already through their plashets.

(In fact, the rhel-9.6-early-kernel repo is just an OCP plashet in disguise; there are excludes added so that only the kernel is permitted. This doesn't break the "el-only" concept because those kernels are RHEL-versioned. It's just that historically we've consumed them through OCP plashets, but ideally in the future we'd have a separate, clearly RHEL-versioned, repo for them... But ideally ideally, when we rebase to rhel-bootc, we have a rhel-bootc stream that uses those kernels that we would derive from.)

[jlebon]

CI will need openshift/release#61361.

This would've been cleaner probably as an rpm-ostree repo-packages-like feature. Though OTOH, the low-tech approach of using excludes is appealing and more universal (e.g. dnf can also use this).

[aaradhak]

LGTM

[jlebon]

CI should pass now.

/retest

[aaradhak]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaradhak, jlebon

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 [aaradhak,jlebon]

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

[jlebon]

Just going to force this in. The extensions container is hitting the same issue as openshift/release#61040 (comment). But we're doing this to fix the RHCOS pipeline in the first place.

/override ci/prow/e2e-aws
/override ci/prow/images
/label acknowledge-critical-fixes-only

[openshift-ci-robot]

@jlebon: This pull request explicitly references no jira issue.

Details

In response to this:

We need to enable the rhel-9.6-early-kernel repo to ensure that we still get access to the early kernels. Non-el-only variants (like ocp-rhel-9.6) get this already through their plashets.

(In fact, the rhel-9.6-early-kernel repo is just an OCP plashet in disguise; there are excludes added so that only the kernel is permitted. This doesn't break the "el-only" concept because those kernels are RHEL-versioned. It's just that historically we've consumed them through OCP plashets, but ideally in the future we'd have a separate, clearly RHEL-versioned, repo for them... But ideally ideally, when we rebase to rhel-bootc, we have a rhel-bootc stream that uses those kernels that we would derive from.)

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]

@jlebon: Overrode contexts on behalf of jlebon: ci/prow/e2e-aws, ci/prow/images

Details

In response to this:

Just going to force this in. The extensions container is hitting the same issue as openshift/release#61040 (comment). But we're doing this to fix the RHCOS pipeline in the first place.

/override ci/prow/e2e-aws
/override ci/prow/images
/label acknowledge-critical-fixes-only

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]

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