Passes all tests, root & rootless, local & remote
today's [3.4.4-1.fc35])https://koji.fedoraproject.org/koji/buildinfo?buildID=1864883) passes all tests: root & rootless, local & remote. I will update with karma once that build gets attached here.
Pretty serious case of the systemd sandbox bug.
Ran podman system tests against podman @ https://github.com/containers/podman/pull/12218. pod
tests fail with catatonit-0.1.6-1.fc34
, pass with 0.1.7-1
. LGTM.
Ran podman system tests with podman @ c8790bfbbb845450608adc7a0a03b77979165f42 (vrothberg's catatonit-pause PR). Test suite (pod tests) fails with catatonit-0.1.6-1.fc35.x86_64
, succeeds with 0.1.7-1
. LGTM.
The podman-remote errors are flakes, issue 12052 under discussion right now. I see no option but to waive.
Seems to be manifesting a known stty flake, but otherwise LGTM
Test failures are in podman-remote only, and they're very weird. I've filed podman issue 12052, and I recommend waiving this result.
podman rootless was fixed by https://github.com/containers/podman/pull/11853 (which is presumably not in this build)
podman-remote rootless is a flake that only seems to happen in bodhi, never in CI or my test environment: https://github.com/containers/podman/issues/11825
LGTM, I'm totally fine with waiving.
This will need to be waived. Rootless tests will never pass (my fault, bug in the tests themselves)
Tests will need to be waived. Rootless will never pass, it's a bug (mine) in the tests.
This can be waived. I've filed 11827 for the ACK flake. The other one is a real bug (in the tests, not podman), my fault, and is not a flake.
Yuk. New failure, almost certainly a flake, in rootless remote:
not ok 253 podman network connect/disconnect with port forwarding
# (from function `die' in file ./helpers.bash, line 448,
# from function `run_podman' in file ./helpers.bash, line 221,
# in test file ./500-networking.bats, line 419)
# `run_podman network connect $netname2 $cid' failed with status 56
# $ podman-remote rm --all --force
# $ podman-remote ps --all --external --format {{.ID}} {{.Names}}
# $ podman-remote images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
# quay.io/libpod/testimage:20210610 9f9ec7f2fdef
# $ podman-remote network create testnet-vkwfjR0iF5
# /home/testuser/.config/cni/net.d/testnet-vkwfjR0iF5.conflist
# $ podman-remote network create testnet2-r1Pk2IBwSy
# /home/testuser/.config/cni/net.d/testnet2-r1Pk2IBwSy.conflist
# $ podman-remote run -d --network testnet-vkwfjR0iF5 quay.io/libpod/testimage:20210610 top
# d797adabc97d62a5a8e35072f15f0aaf68d6e73c56a61e0485b5092fdfdaea47
# $ podman-remote run -d -p 5436:80 --network testnet-vkwfjR0iF5 -v /tmp/podman_bats.FQTGpZ/hello.txt:/var/www/index.txt:Z -w /var/www quay.io/libpod/testimage:20210610 /bin/busybox-extras httpd -f -p 80
# 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e
# $ podman-remote inspect 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e --format {{(index .NetworkSettings.Networks "testnet-vkwfjR0iF5").IPAddress}}
# 10.89.0.3
# $ podman-remote inspect 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e --format {{(index .NetworkSettings.Networks "testnet-vkwfjR0iF5").MacAddress}}
# fe:49:35:79:32:82
# $ podman-remote network disconnect testnet-vkwfjR0iF5 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e
# $ podman-remote network connect testnet-vkwfjR0iF5 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e
# $ podman-remote inspect 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e --format {{(index .NetworkSettings.Networks "testnet-vkwfjR0iF5").IPAddress}}
# 10.89.0.4
# $ podman-remote inspect 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e --format {{(index .NetworkSettings.Networks "testnet-vkwfjR0iF5").MacAddress}}
# 2e:f5:32:c7:e9:ba
# $ podman-remote network connect testnet2-r1Pk2IBwSy 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e
# Error: error configuring network namespace for container 9be6ff480a33b24994ce3f73d308398226b880e67abaabcf6e1cd35ab7d8e19e: error adding pod tender_proskuriakova_tender_proskuriakova to CNI network "testnet2-r1Pk2IBwSy": dnsname error: dnsmasq failed with "\ndnsmasq: failed to create inotify: Too many open files\n": exit status 5
# [ rc=125 (** EXPECTED 0 **) ]
Grrr. Two more flakes. One in root:
not ok 155 podman kill - test signal handling in containers
# (from function `die' in file ./helpers.bash, line 448,
# from function `kill_and_check' in file ./130-kill.bats, line 45,
# in test file ./130-kill.bats, line 51)
# `kill_and_check $s' 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 quay.io/libpod/testimage:20210610 sh -c for i in 1 2 3 4 5 6 8 10 12 13 14 15 16 20 21 22 23 24 25 26 64; do trap "echo got: $i" $i; done;
# echo READY;
# while ! test -e /stop; do sleep 0.05; done;
# echo DONE
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 2 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 12 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 20 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 21 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 14 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 4 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 15 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 13 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 24 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 10 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 25 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 8 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 16 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 5 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 1 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 6 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 3 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 26 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 23 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 64 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# # podman kill -s 22 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# 831b20c17247ed29a6eb5a81ee5cbe4bcb2911a5cc309eaab1d732018b73676f
# #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
# #| FAIL: Timed out: no ACK for kill -s 22
# #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...one rootless:
not ok 173 podman volume import test
# (from function `die' in file ./helpers.bash, line 448,
# from function `run_podman' in file ./helpers.bash, line 221,
# in test file ./160-volumes.bats, line 195)
# `run_podman volume export my_vol --output=$tarfile' failed with status 125
# $ 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 volume rm -a
# $ podman volume create my_vol
# my_vol
# $ podman run --rm -v my_vol:/data quay.io/libpod/testimage:20210610 sh -c echo hello >> /data/test
# $ podman volume create my_vol2
# my_vol2
# $ podman volume export my_vol --output=hello5v4yx6mbek.tar
# Error: Could not create tarball file 'hello5v4yx6mbek.tar': open hello5v4yx6mbek.tar: permission denied
# [ rc=125 (** EXPECTED 0 **) ]
# #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
# #| FAIL: exit code is 125; expected 0
# #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The root one, I have no idea, I've never seen it before. The rootless one, I have a bad feeling about (that it's my fault). Will retry once more.
rootless failed. I'm calling it a flake.
Works fine with conmon-2.0.30-1.fc36
LGTM. Fixes the exec /no/such/command bug
Gating test failure is expected:
nothing provides conmon >= 2:2.0.30-1 needed by podman-3:3.4.0-0.3.rc1.fc36.x86_64
I'm running tests manually, will provide feedback and karma as appropriate - perhaps very late tonight, perhaps early tomorrow morning (lots of test runs, will take a long time).
LGTM
Passes all system tests, root & rootless, local & remote