Package: autopkgtest
Version: 5.38
Severity: important

Discovered while trying to run the test suite to release
autopkgtest 5.39[1].

debian/tests/autopkgtest assumes that the ChrootRunner test will succeed
when run as root in a testbed.

But in an autopkgtest-virt-podman container (with or without systemd as
init), it does not, because podman containers don't have CAP_SYS_ADMIN in
the capability bounding set unless we specifically ask for it:

185s 11:11:12 O: test_add_apt_release (__main__.ChrootRunner.test_add_apt_release)
186s 11:11:13 E: mount: /tmp/autopkgtest.test.kheayapd/chroot/dev: permission denied.
186s 11:11:13 O: --add-apt-release ... ERROR
186s 11:11:13 E: dmesg(1) may have more information after failed mount system call.

(see also #1078205 which is another effect of podman not giving us CAP_SYS_ADMIN)

As per doc/README.package-tests.rst, needs-root or needs-sudo does
not guarantee full capabilities in the absence of isolation-machine,
so this particular part of the test should be skipped if CAP_SYS_ADMIN
is not in the capability bounding set. (This is why I'm reporting this
as a bug in the test suite, not a bug in a-v-podman.)

smcv

[1] it is much faster than it used to be, and now "only" takes 1h47 on my
laptop even though I'm additionally trying to run tests in podman now,
where it previously took about 3 hours - many thanks to whoever
provided that speedup!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)