This bug was fixed in the package corosync-qdevice - 3.0.0-4ubuntu1
---
corosync-qdevice (3.0.0-4ubuntu1) eoan; urgency=medium
* Skip autopkgtest for unprivileged containers: (LP: #1837090)
- d/t/control: mark corosync-qnetd test as skippable
- d/t/qdevice: skip if memlock
Thank you!
TODO (mine): observe excuses now only and check if it passes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837090
Title:
corosync-qdevice (3.0.0-2ubuntu1 to 3.0.0-4) autopkgtests
The attachment "corosync-qdevice_3.0.0-4ubuntu1.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
Uploaded:
$ dput ubuntu corosync-qdevice_3.0.0-4ubuntu1_source.changes
Checking signature on .changes
gpg: /home/ubuntu/x/corosync-qdevice_3.0.0-4ubuntu1_source.changes: Valid
signature from AC983EB5BF6BCBA9
Checking signature on .dsc
gpg: /home/ubuntu/x/corosync-qdevice_3.0.0-4ubuntu1.dsc: Valid
** Patch added: "corosync-qdevice_3.0.0-4ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/corosync-qdevice/+bug/1837090/+attachment/5281646/+files/corosync-qdevice_3.0.0-4ubuntu1.debdiff
** Description changed:
+ [Impact]
+
+ * All autopkgtests that rely on corosync won't work
NOTE:
ulimit -H -l unlimited 2>/dev/null || {
# https://bugs.launchpad.net/bugs/1828228
echo "test disabled for unprivileged namespaces"
exit 77
}
This is the test we are using to check if autopkgtest is running in an
unprivileged container (as root, with "needs_root" work in
To prove, I ran the autopkgtest in a unprivileged LXD:
Importing signed cluster certificate
Notice: Trust flag u is set automatically if the private key is present.
pk12util: PKCS12 EXPORT SUCCESSFUL
Certificate stored in /etc/corosync/qdevice/net/nssdb/qdevice-net-node.p12
Reloading
corosync-qdevice tests corosync daemon (obviously) and it is currently
failing armhf only. That happens, specially now, because we've disabled
corosync tests (and daemon startup) for unprivileged armhf containers
(since it won't support memset max limit setting, that corosync daemon
requires).
This is blocking:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1837064
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837090
Title:
corosync-qdevice (3.0.0-2ubuntu1 to 3.0.0-4)
