MGMT-19632: Extending the e2e job to validate the kernel-rt versions matches.

[ybettan]

We are validating that the DTK image contain the kernel packages matching the running kernel on the node.

This commit is extending the job to also compare DTK's kernel-rt packages and the RT kernel that the node will reboot into if configured to do so.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ybettan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ybettan]

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

[ybettan]

/hold

I want to make sure it fails on a clusterbot cluster with a broken sync between kernel and kernel-rt in it.

[ybettan]

/unhold

The test is failing as expected.

+ echo '## TEST: Checking that kernel-rt version in driver-toolkit matches the node ##'
## TEST: Checking that kernel-rt version in driver-toolkit matches the node ##
+ test_kernel_rt_version
++ oc get clusterversion -o yaml
++ yq '.items[0].status.desired.version'
+ ocp_version=4.17.8
++ oc adm release info quay.io/openshift-release-dev/ocp-release:4.17.8-x86_64 --image-for=rhel-coreos-extensions
+ rhel_coreos_extensions_image=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b47aa41d9f732ae42fd4a9f607caecf16478eeb000c5c1f6b8c869b096dcc48b
++ podman run -it --rm quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b47aa41d9f732ae42fd4a9f607caecf16478eeb000c5c1f6b8c869b096dcc48b ls /usr/share/rpm-ostree/extensions/
++ grep -oP 'kernel-rt-\K[0-9]+(\.[0-9]+)*-[0-9]+(\.[0-9]+)*\.[a-z0-9_]+(\.[a-z0-9_]+)*(?=\.rpm)'
+ node_kernel_rt=5.14.0-427.47.1.el9_4.x86_64
+ echo 'INFO: Node kernel-rt: 5.14.0-427.47.1.el9_4.x86_64'
INFO: Node kernel-rt: 5.14.0-427.47.1.el9_4.x86_64
++ get_driver_toolkit_release_file
++ driver_toolkit_release=/tmp/ci-artifacts_20250106124630/driver-toolkit-release.json
++ [[ ! -s /tmp/ci-artifacts_20250106124630/driver-toolkit-release.json ]]
++ echo /tmp/ci-artifacts_20250106124630/driver-toolkit-release.json
+ dtk_release_file=/tmp/ci-artifacts_20250106124630/driver-toolkit-release.json
++ cat /tmp/ci-artifacts_20250106124630/driver-toolkit-release.json
++ jq -r .RT_KERNEL_VERSION
++ cut -d+ -f1
+ dtk_kernel_rt=5.14.0-427.42.1.el9_4.x86_64
+ echo 'INFO: driver-toolkit kernel-rt: 5.14.0-427.42.1.el9_4.x86_64'
INFO: driver-toolkit kernel-rt: 5.14.0-427.42.1.el9_4.x86_64
+ echo 5.14.0-427.42.1.el9_4.x86_64
+ echo 5.14.0-427.47.1.el9_4.x86_64
+ [[ 5.14.0-427.42.1.el9_4.x86_64 != 5.14.0-427.47.1.el9_4.x86_64 ]]
+ echo 'ERROR: driver-toolkit and node kernel-rt version mismatch: (5.14.0-427.42.1.el9_4.x86_64 !=  5.14.0-427.47.1.el9_4.x86_64)'
ERROR: driver-toolkit and node kernel-rt version mismatch: (5.14.0-427.42.1.el9_4.x86_64 !=  5.14.0-427.47.1.el9_4.x86_64)
+ exit 1
+ cleanup
+ oc delete ns openshift-e2e-driver-toolkit
namespace "openshift-e2e-driver-toolkit" deleted

[ybettan]

/assign @yevgeny-shnaidman @TomerNewman

[ybettan]

This job runs on every nightly and gated by ART. A nightly with this job failing cannot be promoted to a z-stream. After merge, it will also gate broken releases (with a broken DTK image) from being promoted into a z-stream.

[yevgeny-shnaidman]

/lgtm

[openshift-ci]

@ybettan: all tests passed!

Full PR test history. Your PR dashboard.

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.

[openshift-ci-robot]

@ybettan: This pull request references MGMT-19632 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

We are validating that the DTK image contain the kernel packages matching the running kernel on the node.

This commit is extending the job to also compare DTK's kernel-rt packages and the RT kernel that the node will reboot into if configured to do so.

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.

[ybettan]

/jira refresh

[openshift-ci-robot]

@ybettan: This pull request references MGMT-19632 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

/jira refresh

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: driver-toolkit
This PR has been included in build driver-toolkit-container-v4.19.0-202501070436.p0.g606c3ee.assembly.stream.el9.
All builds following this will include this PR.