Bug#934992: network-manager breaks systemd autopkgtest

[Andreas Henriksson]

Hi,

I had a quick look and hoping my incomplete findings might be helpful...

On Sat, Aug 17, 2019 at 09:23:17PM +0200, Paul Gevers wrote:
[...]
> With a recent upload of network-manager the autopkgtest of systemd fails
> in testing when that autopkgtest is run with the binary packages of
> network-manager from unstable.
[...]

>From the autopkgtest log:

<<<<<<<<<<<snip>>>>>>>>>>>>>
autopkgtest [12:20:19]: test boot-smoke: [-----------------------
reboot #0
bash: line 1:  6405 Killed                  /tmp/autopkgtest-lxc.d0a1dm24/downtmp/build.Yzc/src/debian/tests/boot-smoke 2> >(tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stderr >&2) > >(tee -a /tmp/autopkgtest-lxc.d0a1dm24/downtmp/boot-smoke-stdout)
autopkgtest [12:20:20]: test process requested reboot with marker 1
checking for failed unmounts for user systemd
checking for connection timeouts
checking that polkitd runs
autopkgtest [12:20:31]: test boot-smoke: -----------------------]
autopkgtest [12:20:32]: test boot-smoke:  - - - - - - - - - - results - - - - - - - - - -
boot-smoke           FAIL non-zero exit status 1
<<<<<<<<<<<snip>>>>>>>>>>>>>


Given the above above output I assume this is where we bail out (note:
script is 'set -e'):
https://sources.debian.org/src/systemd/241-7/debian/tests/boot-smoke/#L51
(Otherwise we should have seen the "checking that there are no running
jobs" output as well.)

So apparently polkitd is not running after the first reboot attempt. I
have no clue why or how to investigate why so I guess I'll leave that to
the professionals.

Maybe it would be useful to change the test to do
"pidof polkitd || fail" to gather more autopkgtest artifacts information
for debugging purposes? i.e. the boot-smoke-journal.txt file.

HTH

Regards,
Andreas Henriksson