This bug was fixed in the package corosync - 3.1.10-3ubuntu1
---------------
corosync (3.1.10-3ubuntu1) stonking; urgency=medium
* Merge with Debian unstable (LP: #2163539). Remaining changes:
- d/t/quorumtool: search for localhost instead of node1
- d/p/Make-the-example-config-valid.patch: comment out the node name
in config file. With this, we will keep the same behavior as we
have in Bionic which is using the output of "uname -n" as the node
name (LP #1874719).
- d/p/lp1918735/0001-allow_knet_handle_fallback_default_yes.patch:
Retry knet_handle_new without privileged flag (LP #1918735).
corosync (3.1.10-3) unstable; urgency=medium
* Team Upload
* [0963378] drop "Rules-Requires-Root: no": it is the default now
* [cd54b86] rewrite d/watch in v5 format
[ Luca Boccassi ]
* [5cc793a] Drop unused adduser dependency.
The adduser call was removed in 733e0c04 (2015),
but the dependency was never cleaned up.
-- Renan Rodrigo <[email protected]> Wed, 19 Aug 2026 15:13:57 -0300
** Changed in: corosync (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2163539
Title:
Merge corosync 3.1.10-3 from Debian for stonking cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/2163539/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
