Hi Lukas, did you actually intend to comment to this bug? I fail to see the link between runlevel(8) returning unknown and apparmor confinement.
-- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/1998943 Title: wait_booted() times out on systems with broken sysvinit compat Status in autopkgtest package in Ubuntu: New Bug description: The wait_booted() function in lib/VirtSubproc.py uses `runlevel` to get the current SysV runlevel, and only considers the test bed booted if `runlevel` returns a valid number. This is fine in most cases, but causes the test bed to timeout if this SysVinit compatibility is broken for some reason. Since Ubuntu runs systemd, it would be better to also check e.g. if multi-user.target is active, since SysVinit programs/interfaces are only left around in systemd for compatibility. I came across this in a PPA autopkgtest where privileged LXD containers broke systemd-tmpfiles-setup.service, which is responsible for creating /var/run/utmp, which is needed for utmpx functions (i.e. how runlevel is stored on the system). Even though the container was booted and running "OK", autopkgtest timed out waiting for the test bed to boot: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar- enr0n-systemd/lunar/amd64/s/systemd/20221130_112430_66c56@/log.gz(look for the line '<VirtSubproc>: failure: timed out waiting for testbed to start; last runlevel "unknown'). I plan on providing a patch for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1998943/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
