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>
