This bug was fixed in the package corosync - 2.4.2-3ubuntu0.17.10.1 --------------- corosync (2.4.2-3ubuntu0.17.10.1) artful; urgency=high
* 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. -- Eric Desrochers <eric.desroch...@canonical.com> Mon, 26 Feb 2018 08:49:19 -0500 ** Changed in: corosync (Ubuntu Artful) Status: Fix Committed => Fix Released ** Changed in: pacemaker (Ubuntu Artful) Status: Fix Committed => 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