Skip to content
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.

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

Wrong kernel packages in driver-toolkit image #2061

Open
bernhardloos opened this issue Nov 27, 2024 · 2 comments
Open

Wrong kernel packages in driver-toolkit image #2061

bernhardloos opened this issue Nov 27, 2024 · 2 comments
Assignees

Comments

@bernhardloos
Copy link

Describe the bug
As far as I understand, the version of the kernel packages installed into the driver-toolkit image corresponding to a SCOS release should exactly match the actual running kernel, but this doesn't seem to be the case:

OKD Version SCOS Version Kernel Version Kernel Version in DTK image
4.16.0-okd-scos.1 416.9.202411211032-0 5.14.0-531.el9.x86_64 5.14.0-460.el9.x86_64
4.17.0-okd-scos.ec.3 417.9.202410282133-0 5.14.0-522.el9.x86_64 5.14.0-452.el9.x86_64
@BeardOverflow
Copy link

BeardOverflow commented Nov 28, 2024

I can confirm this. To test it:

  1. SCOS Version
podman run --rm $(podman run --rm quay.io/okd/scos-release:4.17.0-okd-scos.ec.3 image stream-coreos) cat /etc/os-release | grep OSTREE_VERSION
  1. Kernel Version in SCOS ostree
podman run --rm $(podman run --rm quay.io/okd/scos-release:4.17.0-okd-scos.ec.3 image stream-coreos) rpm -qa | grep kernel-modules-core
  1. Kernel Version in DTK image
podman run --rm $(podman run --rm quay.io/okd/scos-release:4.17.0-okd-scos.ec.3 image driver-toolkit) rpm -qa | grep kernel-modules-core

And this issue is considerably important (repo for usage instructions here: https://github.com/openshift/driver-toolkit). However, for a long time, scos-4.17 had served SCOS 418 version and it was recently fixed (less than a month ago), so I imagine they are working on it.

image

Also, I test the nightly builds for 4.16, 4.17, 4.18 and 4.19. The issue seems to persist.

OKD Version SCOS Version Kernel Version Kernel Version in DTK image
4.16.0-okd-scos.1 (alias 4.16.0-0.okd-scos-2024-11-22-061845) 416.9.202411211032-0 5.14.0-531.el9.x86_64 5.14.0-460.el9.x86_64
4.16.0-0.okd-scos-2024-11-28-101812 416.9.202411271032-0 5.14.0-533.el9.x86_64 5.14.0-460.el9.x86_64
4.17.0-okd-scos.ec.4 (alias 4.17.0-0.okd-scos-2024-11-22-111428) 417.9.202411212033-0 5.14.0-531.el9.x86_64 5.14.0-452.el9.x86_64
4.17.0-0.okd-scos-2024-11-28-122530 417.9.202411272038-0 5.14.0-533.el9.x86_64 5.14.0-452.el9.x86_64
4.18.0-0.okd-scos-2024-11-28-190431 419.9.202411280632-0 5.14.0-533.el9.x86_64 5.14.0-529.el9.x86_64
4.19.0-0.okd-scos-2024-11-28-025810 418.9.202411270632-0 5.14.0-533.el9.x86_64 5.14.0-529.el9.x86_64

Please, note additional issues:

  • Kernel modules above DTK modules for scos-4.19
  • SCOS 418 for scos-4.19 and SCOS 419 for scos-4.18

@Prashanth684
Copy link

Thanks for reporting this! I have filed https://issues.redhat.com/browse/OKD-230. Typically - the way these are built, there is no synchronization between the release payload builds and the scos bootimage builds. We will have to work with the coreos team to figure out a plan once they deliver pure centos bootimages.

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

No branches or pull requests

3 participants