Your message dated Sun, 30 Aug 2026 23:34:22 +0000
with message-id <[email protected]>
and subject line Bug#1144775: fixed in corosync 3.1.10-4
has caused the Debian Bug report #1144775,
regarding corosync: autopkgtest fails under incus-lxc: Could not initialize
corosync configuration API error 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1144775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144775
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: corosync
Source-Version: 3.1.10-4
Done: Ferenc Wágner <[email protected]>
We believe that the bug you reported is fixed in the latest version of
corosync, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ferenc Wágner <[email protected]> (supplier of updated corosync package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 31 Aug 2026 00:46:42 +0200
Source: corosync
Architecture: source
Version: 3.1.10-4
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers
<[email protected]>
Changed-By: Ferenc Wágner <[email protected]>
Closes: 1144775
Changes:
corosync (3.1.10-4) unstable; urgency=medium
.
* [8ebf4cc] Start the autopkgtest daemon in unprivileged containers.
With its default config the Corosync daemon fails to start in
unprivieged containers. While the original LXC autopkgtest backend
allowed the required socket operations, the new Incus backend is more
strict, so the tests need to enable the unprivileged fallback in the
Corosync configuration. (Closes: #1144775)
* [252f24c] The build system links with the needed libraries only since
wheezy.
So the --as-needed linker flag is not needed, providing an easy
workaround for #1146143.
Checksums-Sha1:
b84f9f6cbd1b84df3c93346e13d4388949b188ea 3503 corosync_3.1.10-4.dsc
bb0d1508acc1205c22b81edb43ebc3d14a7582bf 30112 corosync_3.1.10-4.debian.tar.xz
f4c8c4fe5c70b4203aaf8a77eae41fa8664307ef 17170
corosync_3.1.10-4_amd64.buildinfo
Checksums-Sha256:
cbfdd2faf0f8c63acf7ec41c3626ecf2802a08de7874961b0d9f804c751b1522 3503
corosync_3.1.10-4.dsc
c14f37500e8d5c397a16c10ebadf12bdcd5902766cc590cff5648c052dde40cc 30112
corosync_3.1.10-4.debian.tar.xz
3416685d8c2321a56f2af8165e02c3c098f05b2467616aae2fd1afbb5103db05 17170
corosync_3.1.10-4_amd64.buildinfo
Files:
3a2a7c84e4b9bd7b27d5e2da246b6f48 3503 admin optional corosync_3.1.10-4.dsc
0d68aa6bda735dc89741996a1bb1e2c7 30112 admin optional
corosync_3.1.10-4.debian.tar.xz
1fafd0fdb541516a427ecfa958c3b379 17170 admin optional
corosync_3.1.10-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAmqUuZEACgkQOsj3Fkd+
2yP/Wg//RE60dx9qJnVz+CHNIRdETUA0voTpXgdBLNnNp+qjwSyHlG/0iIHT7UwF
3T91Gz4z6+xeGSgfuneyEfNBwb/xWO/YCPvjIhACxq1J/6BfFhwApmjjdnmk0474
yax8OvfJhjBDS/rPEW1Pss3TC8CoyQVmVlxMEvVHXTh77i+KU0MZT32Kju6Ul968
UIqTtwpiB0D/PDCQlbmmboGqAI8OrH14sUfZIJw7eJ0xzJM56MJ6mWbllcFurjmM
uGFchddMwdBAy5E8Ikp9LkqRjSAK4jk2SRtBuxIxC8tQIlhzSDxQJm5Kh+BzcU6s
SQj8ud9BERZTTNeJx48gNpMeD5yIje79f64L2z72wKpAIHQnyW42mIHsExWuA7cs
rnHzBnkeJuLfROsopvAS0XtGHqG9EBDZi1QYyl3HeUAOWezAlB9XVJvr5kLIy5uJ
wBi2/trEWrB7kmkrPp9lndY67wkF7OnBBbV7vvD2BTCKmhKOu7SlKb3q+F6YV6zb
R2C6GnfvQRDJ8+Q8Nu70x7Gd151pugBOEW3VCK4mgH3v3vamMr9mz3YEe64frmj4
lFLEeUnVVAT1Xl5iHUqk/8CEtykqGynqQZmUi0SWwxj0vS2GQcA4VC/+1zXDsPT4
mgZFu2lTJK1mPFj8ZbE2peVbUVadZz7Q5Xzx7YMwu9JsNMR73lw=
=flWT
-----END PGP SIGNATURE-----
pgpx8HqCi3w9E.pgp
Description: PGP signature
--- End Message ---
