You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
oc adm release info registry.ci.openshift.org/origin/release@sha256:4510c50834c07e71521a68c021320b5e44978245c8031a858f74328e54e89e1c --image-for=driver-toolkit returns an image, so I ran it, and it does, indeed have kernel headers:
However, the nodes are not running that, since it's clearly RHEL8. From a node:
sh-5.2# uname -r
6.5.5-200.fc38.x86_64
Is there any way to actually get 6.5.5-200.fc38 packages? I cant find them on rpmfind or anywhere else. I'm not seeing any other possible way to get the right headers to build modules.
Version
4.14.0-0.okd-2023-12-01-225814 registry.ci.openshift.org/origin/release@sha256:4510c50834c07e71521a68c021320b5e44978245c8031a858f74328e54e89e1c
IPI on AWS
How reproducible
100%
The text was updated successfully, but these errors were encountered:
Things are much simpler in FCOS world - packages don't require subscription to download, so there is no need to use driver-toolkit image. Matching kernel can be downloaded on koji
Is there any way to actually get 6.5.5-200.fc38 packages?
machine-os-content image should have repos enabled:
Describe the bug
We need to build nvidia drivers to enable GPU nodes, and are unable to find kernel headers. I started by just trying to use
rpm-ostree
to install kernel-devel, but the versions don't match. So I stumbled on https://www.redhat.com/en/blog/loading-kernel-modules-to-openshift-nodes-using-coreos-layering and started trying that.oc adm release info registry.ci.openshift.org/origin/release@sha256:4510c50834c07e71521a68c021320b5e44978245c8031a858f74328e54e89e1c --image-for=driver-toolkit
returns an image, so I ran it, and it does, indeed have kernel headers:However, the nodes are not running that, since it's clearly RHEL8. From a node:
Is there any way to actually get
6.5.5-200.fc38
packages? I cant find them on rpmfind or anywhere else. I'm not seeing any other possible way to get the right headers to build modules.Version
4.14.0-0.okd-2023-12-01-225814 registry.ci.openshift.org/origin/release@sha256:4510c50834c07e71521a68c021320b5e44978245c8031a858f74328e54e89e1c
IPI on AWS
How reproducible
100%
The text was updated successfully, but these errors were encountered: