This bug was fixed in the package corosync - 3.1.8-3ubuntu1
---------------
corosync (3.1.8-3ubuntu1) plucky; urgency=medium
* Merge with Debian unstable (LP: #2085225). 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).
-- Athos Ribeiro <athos.ribe...@canonical.com> Tue, 19 Nov 2024
19:26:25 -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/2085225
Title:
Merge corosync from Debian unstable for plucky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/2085225/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
