Our checkpoint/restore integration for cockpit-podman started to fail over the weekend. Reproducible: Always Steps to Reproduce: 1. podman container checkpoint test Actual Results: [root@fedora-rawhide-127-0-0-2-2201 ~]# podman container checkpoint swamped-crate 2025-04-07T11:01:05.054607Z: CRIU checkpointing failed -52. Please check CRIU logfile /var/lib/containers/storage/overlay-containers/831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9/userdata/dump.log: Invalid exchange Error: `/usr/bin/crun checkpoint --image-path /var/lib/containers/storage/overlay-containers/831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9/userdata/checkpoint --work-path /var/lib/containers/storage/overlay-containers/831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9/userdata 831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9` failed: exit status 1 (00.000991) Add ipc ns 11 pid 3192 (00.000993) Will take uts namespace in the image (00.000994) Add uts ns 12 pid 3192 (00.001000) Will take mnt namespace in the image (00.001000) Add mnt ns 13 pid 3192 (00.001005) Will take cgroup namespace in the image (00.001005) Add cgroup ns 14 pid 3192 (00.001006) net: Lock network (00.001007) Running network-lock scripts Error (criu/util.c:640): execvp("iptables-restore", ...) failed: No such file or directory (00.001294) Error (criu/util.c:655): exited, status=1 Error (criu/util.c:640): execvp("ip6tables-restore", ...) failed: No such file or directory (00.001482) Error (criu/util.c:655): exited, status=1 (00.001486) Error (criu/net.c:3137): net: Locking network failed: iptables-restore returned -1. This may be connected to disabled CONFIG_NETFILTER_XT_MARK kernel build config option. (00.001494) net: Unlock network (00.001495) Running network-unlock scripts Error (criu/util.c:640): execvp("iptables-restore", ...) failed: No such file or directory (00.001650) Error (criu/util.c:655): exited, status=1 Error (criu/util.c:640): execvp("ip6tables-restore", ...) failed: No such file or directory (00.001797) Error (criu/util.c:655): exited, status=1 Error (criu/util.c:640): execvp("iptables-restore", ...) failed: No such file or directory (00.002826) Error (criu/util.c:655): exited, status=1 Error (criu/util.c:640): execvp("ip6tables-restore", ...) failed: No such file or directory (00.002976) Error (criu/util.c:655): exited, status=1 (00.002983) Unfreezing tasks into 1 (00.002984) Unseizing 3192 into 1 (00.003004) Error (criu/cr-dump.c:2111): Dumping FAILED. [root@fedora-rawhide-127-0-0-2-2201 ~]# podman container checkpoint swamped-crate 2025-04-07T11:01:05.054607Z: CRIU checkpointing failed -52. Please check CRIU logfile /var/lib/containers/storage/overlay-containers/831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9/userdata/dump.log: Invalid exchange Error: `/usr/bin/crun checkpoint --image-path /var/lib/containers/storage/overlay-containers/831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9/userdata/checkpoint --work-path /var/lib/containers/storage/overlay-containers/831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9/userdata 831d7c00b02a92936c3352da90c842ce3cb1a9796a3468eda6540ffe780716f9` failed: exit status 1
Relevant update packages: podman-5.4.1-1.fc43.x86_64 => podman-5.4.2-1.fc43.x86_64 iptables-nft-1.8.11-4.fc43.x86_64 => iptables-nft-1.8.11-5.fc43.x86_64 And this feels related to https://issues.redhat.com/browse/RHEL-58354?filter=-2
This should be fixed with: https://koji.fedoraproject.org/koji/buildinfo?buildID=2693588 https://bodhi.fedoraproject.org/updates/FEDORA-2025-83f93c7f9a Please let us know if you still see errors.
FEDORA-2025-ef25dec09e (criu-4.1-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ef25dec09e
FEDORA-2025-55ce2ca9f0 (criu-4.1-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-55ce2ca9f0
FEDORA-2025-55ce2ca9f0 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-55ce2ca9f0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-55ce2ca9f0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ef25dec09e has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ef25dec09e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ef25dec09e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d374d8ce17 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d374d8ce17` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d374d8ce17 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-dec654d428 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-dec654d428` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-dec654d428 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-d374d8ce17 (criu-4.1-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-dec654d428 (criu-4.1-2.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.