podman

History

Ed Santiago 8d5f758a1d setup: log results of 'ip addr' Purpose: try to diagnose gating-test failure which looks like a bad combination of netavark + cni Signed-off-by: Ed Santiago <santiago@redhat.com>		2022-05-09 06:26:05 -06:00
..
roles	setup: log results of 'ip addr'	2022-05-09 06:26:05 -06:00
check_results.yml	Yet more ansible muckery, to get test results	2020-05-14 07:14:13 -06:00
README	Complete rewrite of gating tests	2020-04-28 12:30:29 -06:00
test_podman_cgroups_vn.yml	Complete rewrite of gating tests	2020-04-28 12:30:29 -06:00
test_podman_remote.yml	gating tests: run podman-remote too	2021-09-17 14:22:05 -06:00
test_podman.yml	gating tests: run podman-remote too	2021-09-17 14:22:05 -06:00
test_toolbox.yml	Gating tests: run toolbox tests	2021-09-13 09:48:10 -06:00
tests.yml	Quick simple tests for podman	2018-11-13 09:50:53 -07:00

README

I'm sorry. The playbooks here are a much-too-complicated way of saying:

   - test podman (root and rootless) under cgroups v2
   - reboot into cgroups v1
   - repeat the same podman tests

We can't use standard-test-basic any more because, tl;dr, that has to
be the last stanza in the playbook and it doesn't offer any mechanism
for running a reboot in the middle of tests. (I actually found a way
but it was even uglier than this approach).

The starting point is tests.yml . From there:

    tests.yml
      \- test_podman.yml
           |- roles/rootless_user_ready/
           \- test_podman_cgroups_vn.yml    (runs twice: cgroups v2, v1)
                |- roles/set_cgroups/
                \- roles/run_bats_tests/    (runs tests: root, rootless)

Principal result is the file 'artifacts/test.log'. It will contain
one line for each test run, format will be '(PASS|FAIL|ERROR) <test name>'

For each completed test there will also be a 'test.<name>.bats.log'
containing some setup blurbs (RPMs, environment) and the full BATS log.