>From Corosync 2.4.1 Release Notes:
This release contains fix for one regression and few more smaller fixes.
"""
During 2.3.6 development the bug which is causing pacemaker to not work after
corosync configuration file is reloaded happened. Solution is ether to use this
fixed version (recommended) or as a quick workaround (for users who wants to
stay on 2.3.6 or 2.4.0) is to create file pacemaker (file name can be
arbitrary) in /etc/corosync/uidgid.d directory with following content (you can
also put same stanza into /etc/corosync/corosync.conf):
uidgid {
gid: haclient
}
"""
Anyone relying in Trusty or Xenial corosync:
corosync | 2.3.3-1ubuntu1 | trusty
corosync | 2.3.3-1ubuntu4 | trusty-updates
corosync | 2.3.5-3ubuntu1 | xenial
corosync | 2.3.5-3ubuntu2.3 | xenial-security
corosync | 2.3.5-3ubuntu2.3 | xenial-updates
should apply the mitigation above, like discovered previously by
commenters of this bug.
Note: Trusty is already EOS so I'm marking it as "won't fix".
Xenial should include the mitigation in a SRU.
** Changed in: pacemaker (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: pacemaker (Ubuntu Trusty)
Importance: Medium => Undecided
** Changed in: pacemaker (Ubuntu Xenial)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
Title:
Pacemaker unable to communicate with corosync on restart under lxc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/+subscriptions
--
Ubuntu-server-bugs mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
