This bug was fixed in the package pacemaker - 1.1.17+really1.1.16-1ubuntu2 --------------- pacemaker (1.1.17+really1.1.16-1ubuntu2) artful; urgency=medium
* Rebuilding with a version greater than 1.1.17: - pacemaker 1.1.17 was pushed to Artful at one point and then got deleted. pacemaker (1.1.16-1ubuntu2) artful; urgency=high * Fix FBTFS situations - d/p/crm-mon-protect-against-non-standard-or-failing-asctime.patch: Fix: crm_mon: protect against non-standard or failing asctime. - d/libcrmservice3.symbols: Mark symbols optional to avoid FTBFS with newer toolchains and make it cleanly backportable to older toolchains. * Properly restart corosync and pacemaker together (LP: #1740892) - d/pacemaker.preinst: flag corosync to restart pacemaker on upgrade. -- Eric Desrochers <eric.desroch...@canonical.com> Mon, 26 Feb 2018 12:36:37 -0500 ** Changed in: corosync (Ubuntu Xenial) 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