Source: corosync
Version: 3.1.10-3
Severity: important
Justification: fails autopkgtest on Debian CI infrastructure
Tags: forky sid
User: [email protected]
Usertags: lxc

Hi,

Debian CI is switching away from lxc containers in favor of incus Containers.
This is motivated by security concerns from us; incus is based on lxc, but
orchestrates containers substantially different: containers are not privileged
(so root in the container is not uid 0 outside of it, and incus imposes a
stricter isolation from the host system.

corosync passes its tests under lxc, but fails under incus.
The relevant part of the failure is (hopefully):

> Setting up libcmap4:amd64 (3.1.10-3) ...
> Setting up libquorum5:amd64 (3.1.10-3) ...
> Setting up xsltproc (1.1.45-0.1) ...
> Setting up libsam4:amd64 (3.1.10-3) ...
> Setting up libnss3:amd64 (2:3.126-1) ...
> Setting up libnl-route-3-200:amd64 (3.12.0-2+b1) ...
> Setting up libreadline8t64:amd64 (8.3-4) ...
> Setting up libknet1t64:amd64 (1.33-1+b1) ...
> Setting up libcorosync-common-dev:amd64 (3.1.10-3) ...
> Setting up libsnmp45:amd64 (5.9.5.2+dfsg-2.1+b2) ...
> Setting up corosync-vqsim (3.1.10-3) ...
> Setting up libquorum-dev:amd64 (3.1.10-3) ...
> Setting up libcfg-dev:amd64 (3.1.10-3) ...
> Setting up libvotequorum-dev:amd64 (3.1.10-3) ...
> Setting up libnozzle1t64:amd64 (1.33-1+b1) ...
> Setting up libcmap-dev:amd64 (3.1.10-3) ...
> Setting up libcpg-dev:amd64 (3.1.10-3) ...
> Setting up libsam-dev:amd64 (3.1.10-3) ...
> Setting up corosync (3.1.10-3) ...
> Created symlink 
> '/etc/systemd/system/multi-user.target.wants/corosync.service' → 
> '/usr/lib/systemd/system/corosync.service'.
> Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
> Setting up corosync-notifyd (3.1.10-3) ...
> Created symlink 
> '/etc/systemd/system/multi-user.target.wants/corosync-notifyd.service' → 
> '/usr/lib/systemd/system/corosync-notifyd.service'.
> Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
> Processing triggers for dbus (1.16.2-5+b1) ...
> Processing triggers for libc-bin (2.42-17) ...
> autopkgtest [20:46:09]: test cfgtool: [-----------------------
> Could not initialize corosync configuration API error 2
> autopkgtest [20:46:10]: test cfgtool: -----------------------]
> autopkgtest [20:46:10]: test cfgtool:  - - - - - - - - - - results - - - - - 
> - - - - -
> cfgtool              FAIL non-zero exit status 1


The full autokpgtest logs are available at:
https://ci.debian.net/experiments/8/regressions/
(please beware of pagination)

Common types of failure and suggested fixes are being documented at:
https://wiki.debian.org/ContinuousIntegration/LxcToIncus

Note that for the time being, corosync is still being tested under lxc to
avoid disturbing its testing migration test results.

If you decide to add the `isolation-machine` restriction to get this package
tested under qemu, please mention that explicitly when closing this bug (it's
fine to do that only in the package changelog entry that closes the bug) so
that we can configure your package for qemu on ci.debian.net.

Attachment: signature.asc
Description: PGP signature

Reply via email to