Commit Graph

19 Commits

Author SHA1 Message Date
Ed Santiago
967f9534f2 gating tests: run podman-remote too
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>
2021-09-17 14:22:05 -06:00
Ed Santiago
c461125d7c Gating tests: run toolbox tests
Successful on rawhide as of toolbox-0.0.99.2^3.git075b9a8d2779-7.fc36
on 2021-09-13.

See: https://github.com/containers/podman/issues/10296

Signed-off-by: Ed Santiago <santiago@redhat.com>
2021-09-13 09:48:10 -06:00
Ed Santiago
c085cdcd17 gating tests: include kernel version in Packages output
Signed-off-by: Ed Santiago <santiago@redhat.com>
2021-05-18 10:08:58 -06:00
Ed Santiago
c10ab01751 Sigh. Disable reboot. Disable cgroups v1 test.
There's a nasty bug in the CI infrastructure: reboots
hang forever[1]. Sometimes they work, but only 25% of
the time -- the rest of the time, gating tests fail.

 [1] https://redhat.service-now.com/surl.do?n=PNT0808530

So, let's just disable the reboot and all cgroups v1 tests.
For now, I've disabled with a quick edit that should allow
us to reenable if/when the reboot bug is fixed.

TODO: reevaluate in three months (2020-08). If the reboot
bug is not fixed by then, just scrap the entire cgroups
refactoring and go back to plain standard-test-basic.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2020-05-21 17:37:36 +00:00
Ed Santiago
5dd1bdae66 Yet more ansible muckery, to get test results
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>
2020-05-14 07:14:13 -06:00
Ed Santiago
04f2203e24 WIP: Keep trying to fix ansible
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>
2020-05-13 10:19:19 -06:00
Ed Santiago
712ba62553 Yet more ansible hackery: create results.yml
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>
2020-05-12 06:39:48 -06:00
Ed Santiago
5b50b233ab Sigh. Put the reboot in a block.
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>
2020-05-11 14:12:45 -06:00
Ed Santiago
567c3048f9 Complete rewrite of gating tests
This makes a mess of the gating test sources, all
for the sake of being able to run cgroups v1 tests.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2020-04-28 12:30:29 -06:00
Ed Santiago
4f79062b91 gating-test RPM output: include container-selinux
Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-11-21 16:58:30 -07:00
Ed Santiago
9def1dd905 Gating tests: use loginctl
- instead of hacky mkdir /run/user/<fedora id>,
  use loginctl enable-linger and hope that it
  has the same effect.

  reason: the mkdir doesn't seem to be 100% effective.
  There are cases in which the first rootless podman
  invocation fails with:

    Error: could not get runtime: cannot mkdir /run/user/1000/libpod: mkdir /run/user/1000/libpod: no such file or directory

Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-10-09 14:57:11 -06:00
Ed Santiago
a68b9cccc3 gating tests: also log environment
Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-10-09 06:35:47 -06:00
Ed Santiago
9ca09175b8 gating tests: log important package versions
Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-10-03 08:26:19 -06:00
Ed Santiago
20052717cb rootless: 1 step forward, 1 step back
forward: rhbz1740664 (permissions on /dev/net/tun) appears to
be fixed; let's remove the 'modprobe tun' workaround.

back: rootless tests are failing in CI, in a way that I
can't reproduce via 1minutetip. One of the errors is:

   cannot mkdir /run/user/1000/libpod: mkdir /run/user/1000/libpod: no such file or directory

...so let's try, after the mkdir, chowning it to fedora.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-09-12 15:18:17 -06:00
Ed Santiago
b1820d75a1 Workaround for failing rootless tests bz1740664
Systemd bug 1740664 causes /dev/net/tun to be mode 600,
causing slirp4netns to fail on rootless podman.
Suggested workaround is to 'modprobe tun'. Let's
give that a try in the interests of making the
gating tests pass.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-08-26 09:27:53 -06:00
Bruno Goncalves
2afdae1620 run tests with timeout parameter
timeout parameter is supported by the test role: https://pagure.io/standard-test-roles/blob/master/f/roles/standard-test-basic
2019-08-02 08:47:15 +02:00
Bruno Goncalves
096afbce0b run tests using standard-test-basic role
attempt to run the test also as rootless
2019-07-22 15:04:33 +02:00
Ed Santiago
aea393b7eb New tests subpackage
Define a new podman-tests subpackage, containing a set of
tests intended to be run as gates. As of this initial checkin,
this consists of a set of BATS tests in /usr/share/podman .

Include a configuration for running under Fedora CI

Signed-off-by: Ed Santiago <santiago@redhat.com>
2019-03-13 06:45:03 -06:00
Ed Santiago
7203469f10 Quick simple tests for podman
This is a placeholder only. The idea is that, once the ginkgo
tests are approved and merged and packaged, you add that
package to test_podman.yml:required_packages, then rewrite
the .sh script so it invokes those tests and writes PASS/FAIL
to test.log as appropriate.

Until then, this can serve as a rudimentary gate.

Signed-off-by: Ed Santiago <santiago@redhat.com>
2018-11-13 09:50:53 -07:00