Sorry for the long delay on my end! I have pushed up MPs for the correct resolution (I think) for Bionic (incl. appropriate comments of what can be dropped after B+1 opens).
I am building them in my PPA (pacemaker 1.1.18~rc4-1ubuntu1~ppa1 and corosync 2.4.2-3ubuntu1~ppa1) now and will test the following scenarios: (to level-set) X -> B [should be broken] X -> B + PPA [should work] A -> B [may or may not be broken, because there is not a corosync version change] A -> B + PPA [should work] as well as the prior cases of fresh install in B and reinstall in B. Additionally, we should be able to test starting/stopping/restarting of corosync in B successfully doing the same state to pacemaker. Presuming these tests pass and the Canonical Server Team reviews and approves them, I will upload them this week. Eric & co. at that point, I'm wondering if perhaps your team can pick up the SRUs to X, A and T? I think X and A will take the same changes. As we discussed, we would do the minimum required for the older releases, as in my MPs already up. The only thing currently missing is a debconf note prompt, I think, that says pacemaker will have been stopped by the corosync upgrade and will need to be manually restarted. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
