Fix system test: podman logs restarted journald

When run with `podman-remote`, the `--events-backend` option is
unavailable.  However, the `podman logs restarted journald` test blindly
sets `events_backend` without checking if the remote client is being
used.  This causes the test to fail.  Fix this by skipping the test when
the remote client is being used.

Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
Chris Evich 2026-04-17 10:28:59 -04:00
parent 2440195c03
commit 371c4bd341
No known key found for this signature in database
GPG key ID: 03EDC70FD578067F

View file

@ -120,6 +120,9 @@ ${cid[0]} d" "Sequential output from logs"
function _log_test_restarted() {
local driver=$1
local events_backend=$(_additional_events_backend $driver)
if [[ -n "${events_backend}" ]]; then
skip_if_remote "remote does not support --events-backend"
fi
run_podman run --log-driver=$driver ${events_backend} --name logtest $IMAGE sh -c 'start=0; if test -s log; then start=`tail -n 1 log`; fi; seq `expr $start + 1` `expr $start + 10` | tee -a log'
# FIXME: #9597
# run/start is flaking for remote so let's wait for the container condition