-
Notifications
You must be signed in to change notification settings - Fork 33
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
Image refresh for rhel-9-6 #7004
Conversation
image-refresh rhel-9-6 done: https://github.com/cockpit-project/bots/commits/image-refresh-rhel-9-6-20241017-225558 |
7e5c020
to
991ff7d
Compare
This kdump nfs failure may be real -- there's no new kdump, but a new kernel. Retrying once to compare, then investigating. |
There's indeed a regression. On the main image,
but on the new image it succeeds despite seeing the error:
Same result with This doesn't actually need a running NFS server, can just be tested with
With old kernel-core-5.14.0-516.el9.x86_64 and kexec-tools-2.0.27-16.el9_5.1.x86_64 it correctly fails:
with kexec-tools-2.0.27-17.el9.x86_64 it wrongly succeeds:
It's enough to just update that one package. This was changed in https://gitlab.com/redhat/centos-stream/rpms/kexec-tools/-/merge_requests/245 and it only refers to https://issues.redhat.com/browse/RHEL-32060 which is unrelated. So this doesn't look like an intentional behaviour change, but a bad backport. Reported to https://issues.redhat.com/browse/RHEL-63047 |
Downstream report: https://issues.redhat.com/browse/RHEL-63047 Known issue #7005
991ff7d
to
5e5c314
Compare
Image refresh for rhel-9-6