From 905e21a0a127f8f320c2c41567adf2f1198c21a5 Mon Sep 17 00:00:00 2001 From: Ed Santiago Date: Thu, 11 Jan 2024 13:03:11 -0700 Subject: [PATCH] systests: kube with policies test: fix race Add a wait_for_ready() to one kube-play test, to make sure container output has made it to the journal. Probably does not fix #18501, but I think it might fix its most common presentation. Signed-off-by: Ed Santiago --- test/system/260-sdnotify.bats | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/test/system/260-sdnotify.bats b/test/system/260-sdnotify.bats index c139f53463..fb7cb39f58 100644 --- a/test/system/260-sdnotify.bats +++ b/test/system/260-sdnotify.bats @@ -325,7 +325,7 @@ spec: - command: - /bin/sh - -c - - 'printenv NOTIFY_SOCKET; while ! test -f /stop;do sleep 0.1;done' + - 'printenv NOTIFY_SOCKET; echo READY; while ! test -f /stop;do sleep 0.1;done' image: $SYSTEMD_IMAGE name: a - command: @@ -367,6 +367,7 @@ EOF die "container $container_a and/or $container_b did not start" fi + wait_for_ready $container_a # Make sure the containers have the correct policy run_podman container inspect $container_a $container_b $service_container --format "{{.Config.SdNotifyMode}}" is "$output" "container