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):
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.

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 1144775@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ferenc Wágner <wferi@debian.org> (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 ftpmaster@ftp-master.debian.org)
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 <debian-ha-maintainers@lists.alioth.debian.org>
Changed-By: Ferenc Wágner <wferi@debian.org>
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-----

Control: reopen -1
Control: retitle -1 corosync: autopkgtest fails under incus-lxc: Could not initialize corosync configuration API error CS_ERR_LIBRARY

Unfortunately, corosync still fails under incus-lxc (while passing under
plain lxc).

----------------8<----------------8<----------------8<-----------------
 86s autopkgtest [21:52:13]: test logrotate: [-----------------------
 86s + OUTPUT=/tmp/autopkgtest.UQmpAc/logrotate-artifacts/logrotate.txt
 86s + LOG=/var/log/corosync/corosync.log
 86s + logrotate --force --log /tmp/autopkgtest.UQmpAc/logrotate-artifacts/logrotate.txt /etc/logrotate.d/corosync
 86s Could not initialize corosync configuration API error CS_ERR_LIBRARY
 86s error: error running non-shared postrotate script for /var/log/corosync/corosync.log of '/var/log/corosync/corosync.log'
 86s autopkgtest [21:52:13]: test logrotate: -----------------------]
----------------8<----------------8<----------------8<----------------->

Compare:

lxc       (pass): https://ci.debian.net/packages/c/corosync/testing/amd64/76260411/
incus-lxc (fail): https://ci.debian.net/packages/c/corosync/testing/amd64/76260412/

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 1144775@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ferenc Wágner <wferi@debian.org> (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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 01 Oct 2026 23:01:26 +0200
Source: corosync
Architecture: source
Version: 3.1.10-5
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers <debian-ha-maintainers@lists.alioth.debian.org>
Changed-By: Ferenc Wágner <wferi@debian.org>
Closes: 1144775
Changes:
 corosync (3.1.10-5) unstable; urgency=medium
 .
   * [41f3f4c] Start the autopkgtest daemon in unprivileged containers 2.
     Due to an oversight (and testbed reuse in autopkgtest 5) 8ebf4cc0 in the
     previous upload only fixed two of the three tests. (Closes: #1144775)
Checksums-Sha1:
 7d86b2017bfc0b9d6cfecfdf24fd3aa70b145969 3503 corosync_3.1.10-5.dsc
 3b7718e815bed9ec1ce96989ac4276070cd02871 30212 corosync_3.1.10-5.debian.tar.xz
 2a1700e64103a769b4727ec8ed9d8cef75116c18 17133 corosync_3.1.10-5_amd64.buildinfo
Checksums-Sha256:
 a2d9b177b7aade1f676869b0fe43c2ba92dd773ff49b3a5c7f24533117ea2075 3503 corosync_3.1.10-5.dsc
 e2bce3bd972ad9c6a25aefff0cd45603a59641d62f140472b4600dd7c56748df 30212 corosync_3.1.10-5.debian.tar.xz
 ce22329f05c95e00fd679c61d7766ea1306c5f082201151a7785210aa486f1e2 17133 corosync_3.1.10-5_amd64.buildinfo
Files:
 eade198202aa9f430f3718d3fd5dcfe1 3503 admin optional corosync_3.1.10-5.dsc
 7948b2807518194f4aadd4db7b7fa5d0 30212 admin optional corosync_3.1.10-5.debian.tar.xz
 2ce8bb7a90606bdc9e6ccd0d69231896 17133 admin optional corosync_3.1.10-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAmq+yqkACgkQOsj3Fkd+
2yNeMRAAkTe4mllPpJuqpRQRMfKIsDiW/R05k3Fx2Vfsql0u9gxP+Z6RJQjf1iz3
LnQTdqitno0sNY1kOiWDvua/f9Pkv0b19XQP892/WqY1GDnI0N5QAZpXgQH5uY7V
8JZlK9ZGq3yMSxlVezVATbKxGgyqGz/wSoOr0JSS/WSNr5v30THNLaZAO7fvGSfy
lgSXm7qtd/msSEnUd0p9D+poCJwnl+WQAQnfXU3e2FBfSmBVXxK6c598iWGH6LHj
VpmOlQzQhTerTZ07v8H5wlmK5FLcW3hzW5xpG2p6tQy08Zf9F8+FBHskla37Qult
iqJrQwWeQ359MmgQx5tsScGsbKGLt581EBjzyrurVVKqn+nDEKH8VxnHaaj1SKYL
4uvqHCP7EwgA86tzi+7+gXa5NALYqf8oNq4WT+/EBu+zY2c8g8eNFvdtL8bbPuxW
4bUNsBYkZPlGAhW1/DzIB2BDwy6lT7GH8NzPbbFR/YbjzsX+/VlWrdDUADxi5hgi
nBOPz5Wlk35brlEvlVJnw2Zwu862gOZPgKKI38bkt+lFOm7L5xL1XDLb+tMJr3S/
yHh56Lefe0uXjAhoHLszRtUFBYBDix1CUTkyymnyil8/4+Z0pzWbO0qX1dMFLNEG
DyrS7cpUpwOCCfB2bZiXQNRryr0Iot7uzL1iitqt3Je+3CUGZgU=
=q89p
-----END PGP SIGNATURE-----

Antonio Terceiro <terceiro@debian.org> writes:

Bah, testbed reuse in autopkgtest v5 threw off my testing.  Sorry about
that.  3.1.10-5 should fare better.