checkpoint and restore one container into a new pod using --export fails on Ubuntu 22.04 (ubuntu-latest) #6396
Description
Which jobs are failing?
The integration tests fail in GitHub actions when using the ubuntu-22.04 (ubuntu-latest) runner.
Which tests are failing?
16 checkpoint and restore one container into a new pod using --export
17 checkpoint and restore one container into a new pod using --export to OCI image
18 checkpoint and restore one container into a new pod using --export to OCI image using repoDigest
For example:
16 checkpoint and restore one container into a new pod using --export
…
# (from function `crictl' in file ./helpers.bash, line 204,
# in test file ./checkpoint.bats, line 36)
# `crictl start "$ctr_id"' failed
…
# time="2022-11-23 09:25:30.158968678Z" level=error msg="Container restore error: time=\"2022-11-23T09:25:30Z\" level=warning msg=\"freezer not supported: openat2 /sys/fs/cgroup/pod_123.slice/pod_123-456.slice/crio-3bb2dd752f3b3841e98c6c80077fe5a6f06ec492f8be80d18d589c51b64f4c2f.scope/cgroup.freeze: no such file or directory\"\ntime=\"2022-11-23T09:25:30Z\" level=warning msg=\"lstat /sys/fs/cgroup/pod_123.slice/pod_123-456.slice/crio-3bb2dd752f3b3841e98c6c80077fe5a6f06ec492f8be80d18d589c51b64f4c2f.scope: no such file or directory\"\ntime=\"2022-11-23T09:25:30Z\" level=error msg=\"criu failed: type NOTIFY errno 0\\nlog file: /tmp/tmp.GjK1YejHJe/crio-run/overlay-containers/3bb2dd752f3b3841e98c6c80077fe5a6f06ec492f8be80d18d589c51b64f4c2f/userdata/restore.log\"\n" file="oci/runtime_oci.go:291" id=150a3031-91cc-42ae-b15e-705b60d7dba0 name=/runtime.v1.RuntimeService/StartContainer
# time="2022-11-23 09:25:30.180754860Z" level=debug msg="Response error: failed to restore container 3bb2dd752f3b3841e98c6c80077fe5a6f06ec492f8be80d18d589c51b64f4c2f: container restore failed: time=\"2022-11-23T09:25:30Z\" level=warning msg=\"freezer not supported: openat2 /sys/fs/cgroup/pod_123.slice/pod_123-456.slice/crio-3bb2dd752f3b3841e98c6c80077fe5a6f06ec492f8be80d18d589c51b64f4c2f.scope/cgroup.freeze: no such file or directory\"\ntime=\"2022-11-23T09:25:30Z\" level=warning msg=\"lstat /sys/fs/cgroup/pod_123.slice/pod_123-456.slice/crio-3bb2dd752f3b3841e98c6c80077fe5a6f06ec492f8be80d18d589c51b64f4c2f.scope: no such file or directory\"\ntime=\"2022-11-23T09:25:30Z\" level=error msg=\"criu failed: type NOTIFY errno 0\\nlog file: /tmp/tmp.GjK1YejHJe/crio-run/overlay-containers/3bb2dd752f3b3841e98c6c80077fe5a6f06ec492f8be80d18d589c51b64f4c2f/userdata/restore.log\"\n" file="[email protected]/chain.go:25" id=150a3031-91cc-42ae-b15e-705b60d7dba0 name=/runtime.v1.RuntimeService/StartContainer
https://github.com/cri-o/cri-o/actions/runs/3530716552/jobs/5923020560
Since when has it been failing?
Since ubuntu-latest switched from 20.04 to 22.04.
Testgrid link
None
Reason for failure (if possible)
The error originates from runc 1.1.4: https://github.com/opencontainers/runc/blob/5fd4c4d144137e991c4acebb2146ab1483a97925/libcontainer/cgroups/fs2/freezer.go#L30-L39