corosync-qdevice (3.0.0-2ubuntu1 to 3.0.0-4) autopkgtests regression
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
corosync-qdevice (Ubuntu) |
Fix Released
|
Medium
|
Rafael David Tinoco |
Bug Description
[Impact]
* All autopkgtests that rely on corosync won't work correctly if started in an unprivileged container. This happens because corosync daemon needs some privileged kernel calls that aren't available if UID != 0 (like roots under unprivileged lxd containers).
[Test Case]
* You can try to start corosync daemon in an unprivileged lxd container for any architecture. You will face the bug:
https:/
[Regression Potential]
* Changes are being done only in debian/tests/* files and are being placed only in Eoan so we can pass all excuses, for all HA related packages.
* Best fix here, in a near future, would be to have a way to skip tests if they're running in unprivileged containers.
[Other Info]
ORIGINAL DESCRIPTION
There is an autopkgtest failure for corosync-qdevice:
corosync-qdevice (3.0.0-2ubuntu1 to 3.0.0-4)
Maintainer: Debian HA Maintainers
Section: universe/misc
163 days old
autopkgtest for corosync-
Not considered
For armhf:
Certificate request stored in /etc/corosync/
Signing cluster certificate
Certificate stored in /etc/corosync/
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/
Reloading corosync.conf...
Could not initialize corosync configuration API error CS_ERR_LIBRARY
autopkgtest [17:47:43]: test qdevice: -------
autopkgtest [17:47:46]: test qdevice: - - - - - - - - - - results - - - - - - - - - -
qdevice FAIL non-zero exit status 1
autopkgtest [17:47:48]: @@@@@@@
qnetd PASS
qdevice FAIL non-zero exit status 1
Changed in corosync-qdevice (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Rafael David Tinoco (rafaeldtinoco) |
This is blocking: /bugs.launchpad .net/ubuntu/ +source/ corosync/ +bug/1837064
https:/