From faa2689dcd93bf0fc2b0101daed0d5ac5eb64cc0 Mon Sep 17 00:00:00 2001 From: Valentin Rothberg Date: Mon, 12 Jun 2023 13:18:50 +0200 Subject: [PATCH] 250-systemd.bats: remove outdated comment Remove an outdated comment on the absence of exit-code propagation when running K8s workloads in systemd. The `podman-kube@` systemd template is using default restart policy of the system. The exit-code propagation is tested in other tests, so we can keep the logic as is. Signed-off-by: Valentin Rothberg --- test/system/250-systemd.bats | 3 --- 1 file changed, 3 deletions(-) diff --git a/test/system/250-systemd.bats b/test/system/250-systemd.bats index 8e24440228..ce0be89f7b 100644 --- a/test/system/250-systemd.bats +++ b/test/system/250-systemd.bats @@ -448,9 +448,6 @@ $name stderr" "logs work with passthrough" is "$output" ".*$service_name,.* (test_pod-b),$IMAGE,false,registry.*" "container-specified auto-update policy gets applied" # Kill the pod and make sure the service is not running. - # The restart policy is set to "never" since there is no - # design yet for propagating exit codes up to the service - # container. run_podman pod kill test_pod for i in {0..20}; do run systemctl is-active $service_name