Skip to content

Possible criu v4.1 regression in Fedora #2650

@kolyshkin

Description

@kolyshkin

When criu v4.1 is used in runc CI tests in Fedora 41, it fails like this:

not ok 39 checkpoint and restore in external network namespace
# (in test file tests/integration/checkpoint.bats, line 304)
#   `[ "$status" -eq 0 ]' failed
# runc spec (status=0):
#
# external_net_ns is supported
# runc run -d --console-socket /tmp/bats-run-Z4hgub/runc.XrBtvk/tty/sock test_busybox (status=0):
#
# runc state test_busybox (status=0):
# {
#   "ociVersion": "1.2.1",
#   "id": "test_busybox",
#   "pid": 26103,
#   "status": "running",
#   "bundle": "/tmp/bats-run-Z4hgub/runc.XrBtvk/bundle",
#   "rootfs": "/tmp/bats-run-Z4hgub/runc.XrBtvk/bundle/rootfs",
#   "created": "2025-04-18T00:43:29.896678866Z",
#   "owner": ""
# }
# runc checkpoint --work-path ./work-dir test_busybox (status=0):
#
# runc state test_busybox (status=1):
# time="2025-04-18T00:43:30Z" level=error msg="container does not exist"
# runc restore -d --work-path ./work-dir --console-socket /tmp/bats-run-Z4hgub/runc.XrBtvk/tty/sock test_busybox (status=1):
# time="2025-04-18T00:43:30Z" level=warning msg="--- Quoting \"work-dir/restore.log\""
# time="2025-04-18T00:43:30Z" level=warning msg="382:(00.036384)      1: mnt-v2: Move mount 97 from /tmp/.criu.mntns.IhNw5B/mnt-0000000097 to /tmp/.criu.mntns.IhNw5B/13-0000000000/dev/console"
# time="2025-04-18T00:43:30Z" level=warning msg="383:(00.036402)      1: mnt-v2: Move mount 376 from /tmp/.criu.mntns.IhNw5B/mnt-0000000376 to /tmp/.criu.mntns.IhNw5B/13-0000000000/sys"
# time="2025-04-18T00:43:30Z" level=warning msg="384:(00.036420)      1: mnt-v2: Move mount 380 from /tmp/.criu.mntns.IhNw5B/mnt-0000000380 to /tmp/.criu.mntns.IhNw5B/13-0000000000/sys/fs/cgroup"
# time="2025-04-18T00:43:30Z" level=warning msg="385:(00.036439)      1: mnt-v2: Move mount 113 from /tmp/.criu.mntns.IhNw5B/mnt-0000000113 to /tmp/.criu.mntns.IhNw5B/13-0000000000/sys/firmware"
# time="2025-04-18T00:43:30Z" level=warning msg="386:(00.036451)      1: mnt: Move the root to /tmp/.criu.mntns.IhNw5B/13-0000000000"
# time="2025-04-18T00:43:30Z" level=warning msg="387:Error: Could not process rule: File exists"
# time="2025-04-18T00:43:30Z" level=warning msg="388:create table inet CRIU-9de6ed64-f981-441a-9e"
# time="2025-04-18T00:43:30Z" level=warning msg="389:                  ^^^^^^^^^^^^^^^^^^^^^^^^^^"
# time="2025-04-18T00:43:30Z" level=warning msg="390:(00.045260) Error (criu/net.c:3256): net: Locking network failed using nftables"
# time="2025-04-18T00:43:30Z" level=warning msg="391:(00.045808) mnt: Switching to new ns to clean ghosts"
# time="2025-04-18T00:43:30Z" level=warning msg="392:(00.046057) Error (criu/cr-restore.c:2320): Restoring FAILED."
# time="2025-04-18T00:43:30Z" level=warning msg="393:(00.047228) Error (criu/cgroup.c:1998): cg: cgroupd: recv req error: No such file or directory"
# time="2025-04-18T00:43:30Z" level=warning msg=---
# time="2025-04-18T00:43:30Z" level=error msg="criu failed: type RESTORE errno 0"
# --- teardown ---

The test case source is here: https://github.com/opencontainers/runc/blob/e55fe63aed22520d565d1a3490e1655e839068eb/tests/integration/checkpoint.bats#L271

This is the first time I am seeing this, so I presume it's a regression in criu v4.1. Might be a hash collision but I very much doubt it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions