https://src.fedoraproject.org/fork/plautrba/rpms/lksctp-tools/blob/1.0.18-with-tests/f/tests/tests.yml https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-pr-pipeline/detail/fedora-rawhide-pr-pipeline/2526/artifacts
There's required_packages: kernel-modules. The installed package is kernel-modules-5.5.0-0.rc6.git3.1.fc32.x86_64 [1] but according to kernel-version.txt [2] the running kernel version is 5.5.0-0.rc6.git2.1.fc32.x86_64 and the test fails [3]:
required_packages: kernel-modules
kernel-modules-5.5.0-0.rc6.git3.1.fc32.x86_64
kernel-version.txt
5.5.0-0.rc6.git2.1.fc32.x86_64
modprobe: FATAL: Module sctp not found in directory /lib/modules/5.5.0-0.rc6.git2.1.fc32.x86_64 Run test 'build-test': done. Test's exit code: 1
[1] https://jenkins-continuous-infra.apps.ci.centos.org/blue/rest/organizations/jenkins/pipelines/fedora-rawhide-pr-pipeline/runs/2526/log/?start=0 [2] https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-pipeline/2526/artifact/nvr-verify/logs/kernel_version.txt [3] https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-pr-pipeline/2526/artifact/package-tests/logs/FAIL-str_build-test.log
I can imagine 2 solutions, but neither would be perfect.
is to install kernel-modules by default when preparing the qcow2 to make sure it is the some version of installed kernel. This solution doesn't solve the problem if other kernel related package like kernel-devel or -debuginfo packages are defined on tests.yml.
When preparing the qcow2 we make sure we update the kernel, when installing kernel related packages on tests.yml will match the version. The problem is in case the new kernel is broken and we are not able to boot the VM, for example, every build will be impacted.
I've used a workaround which manually installs the right version:
+ - install-kernel-modules: + run: dnf install -y kernel-modules-`uname -r`
@bookwar it looks like kernel tests are stable [1], what do you think if we enable gating for kernel? In that case it should be safe enough to update kernel when preparing the qcow2.
[1] https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-rawhide-build-pipeline/8713/
Metadata Update from @jimbair: - Issue assigned to bookwar
I believe we hit this problem again - https://src.fedoraproject.org/tests/selinux/pull-request/97
I'm not sure if kernel module package is installed by default in the qcow2. Would be possible for the test to install the kernel module?
I'd expect it's there given that:
$ rpm -q --requires kernel kernel-core-uname-r = 5.7.15-200.fc32.x86_64 kernel-modules-uname-r = 5.7.15-200.fc32.x86_64 $ rpm -q --provides kernel-modules kernel-modules-uname-r = 5.6.15-300.fc32.x86_64
Even though it's possible that there's only kernel-core.
Anyway, we'll try it again with kernel-modules required/installed
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-rawhide-image-test/lastSuccessfulBuild/artifact/artifacts/PASS-str_installed-packages.log
only kernel-core-5.8.0-1.fc33.x86_64 is installed.
kernel-core-5.8.0-1.fc33.x86_64
The test should try to install kernel-modules-`uname -r`
Login to comment on this ticket.