erabo/spiegel_podman
1
0
Fork 0
mirror of https://github.com/podman-container-tools/podman.git synced 2026-08-05 08:25:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

test/system: skip "sdnotify : container" in rootless mode

Browse source 
Skip the "sdnotify : container" test when running in rootless mode.

This test uses socat to listen on the sdnotify socket and verify that
READY=1 notifications are received from the container. In rootless mode
on RHEL 9.2, the READY=1 notification is never received by socat, even
with a 2-second sleep after systemd-notify to ensure message
transmission.

The test consistently sees only MAINPID (sent early in the container
lifecycle) but never receives the READY=1 notification (sent after the
/stop file is created). This indicates the sdnotify relay mechanism
from container to podman to the external socket is not functioning
properly in rootless mode in this environment.

This is consistent with the other two sdnotify tests in
255-auto-update.bats that also require skipping in rootless mode due
to similar notification delivery issues.

Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
Lokesh Mandvekar 2026-02-02 21:26:49 +05:30 • committed by Chris Evich
parent 4ef726cf50
commit 75c7a0dd27
No known key found for this signature in database
GPG key ID: 03EDC70FD578067F
1 changed files with 7 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
test/system/260-sdnotify.bats
View file

@ -132,20 +132,17 @@ READY=1" "sdnotify sent MAINPID and READY"
# These tests can fail in dev. environment because of SELinux.
# quick fix: chcon -t container_runtime_exec_t ./bin/podman
@test "sdnotify : container" {
# Sigh... we need to pull a humongous image because it has systemd-notify.
# (IMPORTANT: fedora:32 and above silently removed systemd-notify; this
# caused CI to hang. That's why we explicitly require fedora:31)
# FIXME: is there a smaller image we could use?
local _FEDORA="$PODMAN_TEST_IMAGE_REGISTRY/$PODMAN_TEST_IMAGE_USER/fedora:31"
# Pull that image. Retry in case of flakes.
run_podman pull $_FEDORA || \
run_podman pull $_FEDORA || \
run_podman pull $_FEDORA
skip_if_rootless "READY=1 notification not received via socat in rootless mode"
# Pull our systemd image. Retry in case of flakes.
run_podman pull $SYSTEMD_IMAGE || \
run_podman pull $SYSTEMD_IMAGE || \
run_podman pull $SYSTEMD_IMAGE
export NOTIFY_SOCKET=$PODMAN_TMPDIR/container.sock
_start_socat
run_podman run -d --sdnotify=container $_FEDORA \
run_podman run -d --sdnotify=container $SYSTEMD_IMAGE \
sh -c 'printenv NOTIFY_SOCKET;echo READY;systemd-notify --ready;while ! test -f /stop;do sleep 0.1;done'
cid="$output"
wait_for_ready $cid