[Debian-ha-maintainers] Bug#979450: booth: autopkgtest fails on ci-worker-ppc64el-01 (but apparently not on other ppc64el workers)

[Valentin Vidic]

On Sat, Jan 09, 2021 at 06:31:06PM +0100, wferi at niif.hu wrote:
> Not offhand.  It certainly failed to start the Corosync daemon (which
> should automatically start after installation, but that's beside the
> point).  So there's ample chance this is a Corosync peculiarity after
> all; can't you see a similar pattern in the Corosync autopkgtest
> results?  I often find myself wishing the logs were available when
> debugging autopkgtest failures.  Before I'm starting to add journal
> dumps everywhere: don't you think it would be sensible to automatically
> add the created journal file (or something equivalent) to the test log
> or artifacts?

I added some more logging in the new package version and it seems to be a mount
permission problem. Perhaps this worker has a different configuration somehow?

autopkgtest [07:22:25]: host ci-worker-ppc64el-01; command line: /usr/bin/autopkgtest --no-built-binaries '--setup-commands=echo '"'"'booth unstable/ppc64el'"'"' > /var/tmp/debci.pkg 2>&1 || true' --user debci --apt-upgrade '--add-apt-source=deb http://incoming.debian.org/debian-buildd buildd-experimental main contrib non-free' --add-apt-release=experimental --pin-packages=experimental=src:glib2.0 --output-dir /tmp/tmp.KhiiPwYCbB/autopkgtest-incoming/unstable/ppc64el/b/booth/10042004 booth -- lxc --sudo --name ci-027-30fed9e8 autopkgtest-unstable-ppc64el
...
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
● corosync.service - Corosync Cluster Engine
     Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2021-01-27 07:35:33 UTC; 11ms ago
       Docs: man:corosync
             man:corosync.conf
             man:corosync_overview
    Process: 2431 ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS (code=exited, status=226/NAMESPACE)
   Main PID: 2431 (code=exited, status=226/NAMESPACE)

Jan 27 07:35:33 ci-027-30fed9e8 systemd[1]: Starting Corosync Cluster Engine...
Jan 27 07:35:33 ci-027-30fed9e8 systemd[2431]: corosync.service: Failed to set up mount namespacing: Permission denied
Jan 27 07:35:33 ci-027-30fed9e8 systemd[2431]: corosync.service: Failed at step NAMESPACE spawning /usr/sbin/corosync: Permission denied
Jan 27 07:35:33 ci-027-30fed9e8 systemd[1]: corosync.service: Main process exited, code=exited, status=226/NAMESPACE
Jan 27 07:35:33 ci-027-30fed9e8 systemd[1]: corosync.service: Failed with result 'exit-code'.
Jan 27 07:35:33 ci-027-30fed9e8 systemd[1]: Failed to start Corosync Cluster Engine.

https://ci.debian.net/data/autopkgtest/unstable/ppc64el/b/booth/10042004/log.gz

-- 
Valentin