This bug was fixed in the package corosync - 2.4.2-3ubuntu1
---------------
corosync (2.4.2-3ubuntu1) bionic; urgency=medium
* Properly restart corosync and pacemaker together (LP: #1740892)
- d/rules: pass --restart-after-upgrade to dh_installinit
- d/control: indicate this version breaks all older pacemaker, to
force an upgrade of pacemaker.
- d/corosync.postinst: if flagged to do so by pacemaker, start
pacemaker on upgrade.
+ This can be dropped after bionic releases as long as the other
changes are maintained.
-- Nishanth Aravamudan <nish.aravamu...@canonical.com> Tue, 30 Jan
2018 16:40:31 -0800
** Changed in: corosync (Ubuntu Bionic)
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/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
