-
Notifications
You must be signed in to change notification settings - Fork 349
Investigate podman checkpoint test failures on centos-stream-10-x86_64 #1759
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
Comments
Ref: containers#1758 (comment) Issue filed: containers#1759 Signed-off-by: Lokesh Mandvekar <[email protected]>
Ref: containers#1758 (comment) Issue filed: containers#1759 Signed-off-by: Lokesh Mandvekar <[email protected]>
Here's the criu failure (from dump.log):
This is the same as checkpoint-restore/criu#2532, is caused by a newer kernel, and was fixed by checkpoint-restore/criu#2539 (December 2024). The fix made its way into criu 4.1 (released in March 2025). For some reason, CentOS Stream 10 still has criu-3.19. So, the fix is to either bump criu to 4.1, or backport checkpoint-restore/criu#2539. |
It's weird that no one has discovered it earlier. |
Ah, I guess this happened because of a recent backport of torvalds/linux@e93d252 to el10 kernel. |
Yes, this is listed in the changelog for the kernel 6.12.0-76.el10:
|
Filed an upstream bug: https://issues.redhat.com/browse/RHEL-93307 |
I believe @adrianreber updated the CRIU package to v4.1 recently in |
I'll consider that a win for Packit and TMT tests :) . |
podman checkpoint tests fail on centos-stream-10-x86_64 env like so:
The text was updated successfully, but these errors were encountered: