lstat /sys/fs/cgroup/devices/machine.slice/libpod-SHA.scope: ENOENT #11784
Description
New flake in f33-root:
[+0920s] not ok 236 podman selinux: shared context in (some) namespaces
# (from function `is' in file test/system/helpers.bash, line 508,
# in test file test/system/410-selinux.bats, line 126)
# `is "$output" "$context_c1" "new container, run with --pid of existing one "' failed
# # podman rm --all --force
# # podman ps --all --external --format {{.ID}} {{.Names}}
# # podman images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
# quay.io/libpod/testimage:20210610 9f9ec7f2fdef
# # podman run -d --name myctr quay.io/libpod/testimage:20210610 top
# 1f043d30e46e9f85a55a13e7bd72f16316cfd56534e42e699d656ffd3d20da09
# # podman exec myctr cat -v /proc/self/attr/current
# system_u:system_r:container_t:s0:c364,c713^@
# # podman run --name myctr2 --ipc container:myctr quay.io/libpod/testimage:20210610 cat -v /proc/self/attr/current
# system_u:system_r:container_t:s0:c364,c713^@
# # podman run --rm --pid container:myctr quay.io/libpod/testimage:20210610 cat -v /proc/self/attr/current
# system_u:system_r:container_t:s0:c364,c713^@time="2021-09-28T17:08:59-05:00" level=warning msg="lstat /sys/fs/cgroup/devices/machine.slice/libpod-11f69a5b1d699bf9ab9e8b5fa8994e43b3ea7c3d0f0d1e1bc0d5bf33d37cccae.scope: no such file or directory"
# #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
# #| FAIL: new container, run with --pid of existing one
# #| expected: 'system_u:system_r:container_t:s0:c364,c713^@'
# #| actual: 'system_u:system_r:container_t:s0:c364,c713^@time="2021-09-28T17:08:59-05:00" level=warning msg="lstat /sys/fs/cgroup/devices/machine.slice/libpod-11f69a5b1d699bf9ab9e8b5fa8994e43b3ea7c3d0f0d1e1bc0d5bf33d37cccae.scope: no such file or directory"'
# #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is not (as of this writing) a flake that will cause a CI failure, because (as of this writing) system tests and integration tests do not check for extra cruft. THIS IS GOING TO CHANGE, at least in system tests.
I cannot reproduce with podman-3.4.0-0.10.rc2.fc33, in 30 minutes of looping, but my cirrus-flake-grep tool shows this happening as far back as June (when I started collecting CI logs). All the instances I see are root; none rootless.