Based on #10 and some testing I did early today, it really feels like this might be a bug in pacemaker when re-connecting to corosync after a restart; I think there are two ways forward on this:
a) corosync package updates should always restart pacemaker b) we should look for a fix in pacemaker to make it more resilient to corosync restarts either would have prevented this issue from occurring in the first place. -- 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
