This bug was fixed in the package corosync - 3.1.6-1ubuntu1 --------------- corosync (3.1.6-1ubuntu1) jammy; urgency=medium
* Merge with Debian unstable (LP: #1946852). Remaining changes: - d/control: corosync binary depends on libqb-dev (LP #1677684). - 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). - d/t/quorumtool: search for localhost instead of node1. - d/t/control: add allow-stderr restriction. -- Miriam EspaƱa Acebal <miriam.esp...@canonical.com> Wed, 12 Jan 2022 11:58:06 +0100 ** 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/1946852 Title: Merge corosync from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1946852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs