- remove all references to cgroups v1. That code never worked,
and "cgroups v2" in test names was misleading because it
implied an alternative. Remove it.
- refactor podman remote and local tests
- clean up docs
- Ansible bitrot cleanup ("this is deprecated, use that")
Tested using 1minutetip but even so this is a big change and
we need to be prepared for fallout in the next bodhi.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Fixes flake: 'dial tcp: lookup cdn03.quay.io: no such host'
Okay, doesn't actually fix as in _fix_, just fix as in "sweep it
under the rug". The actual bug is in systemd-resolved, or in the
quay.io/cloudflare.net DNS nameservers, or in the weird specific
setup for cdn03 (it's a CNAME, compared to cdn01/02 which are A).
Maybe a combination of all of the above. I don't care; I just
want the flakes gone. I realize that this makes our testing
environment different from default Fedora, and am okay with
that because I suspect many Fedora users disable systemd-resolved
as SOP.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Testing Farm 2023-03.1 has updated to a new Ansible
version.
Unfortunately, playbooks using the deprecated `warn:`
parameter for the shell/command modules will fail
because this had been deprecated
This should fix the problem.
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
In headers of gating tests, also include aardvark, netavark,
containers-common, containernetworking-plugins
Signed-off-by: Ed Santiago <santiago@redhat.com>
A small handful of bugs have blocked us from running podman-remote
in gating tests. Those are all fixed; it's time to enable testing.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Looks like the code I copied from standard-test-roles
has changed; let's reincorporate it.
In particular, there is now an annoying step that pulls
logs and artifacts from remote-host:/tmp/artifacts .
Well, that doesn't exist in our case because /tmp may
not survive reboots. Workaround: after completion of
each test, push our local (master) artifacts to remote.
And, fix a typo in results.yml
Signed-off-by: Ed Santiago <santiago@redhat.com>
DO NOT COMMIT.
I'm simply trying to understand why reboot is failing.
This commit adds some debug statements to try to get
a sense for what grubenv looks like.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Gating tests are still failing. Actually, the BATS portion is
all passing, it just seems to be the end part (infrastructure)
that fails. Let's try creating a results.yml file.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Podman gating tests failed:
... back_again.changed): 'dict object' has no attribute 'changed'
Previous error (ignored) was a timeout in the reboot step. I have
no idea how to fix this, so let's try putting the reboot and wait
steps into a 'block' section and removing the '.changed'.
Tested with 1minutetip. Seems to work, but the reboot was quick
so it didn't trigger the same code.
Signed-off-by: Ed Santiago <santiago@redhat.com>