[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

[Nish Aravamudan]

Big thanks to Robie Basak for providing some feedback and discussion on
IRC and in the MP.

We came up with the following, which I'm currently testing, to try and
resolve this issue:

In addition to all the changes currently in the MP(s), modify:

corosync to Breaks: on older pacemaker versions than the one we are going to provide in this update
pacemaker's preinst to mark via a file in /run if pacemaker is running, if upgrading from an older version of pacemaker
corosync's postinst to check the file in /run and start pacemaker, if upgrading from an older version of corosync

The effect of these changes together is to force corosync to upgrade
pacemaker (via the Breaks) and for pacemaker to indicate to corosync
whether it should start pacemaker in the maintainer scripts.

The currently building versions for Trusty in my PPA (corosync =
2.3.3-1ubuntu4.1~ppa4 and pacemaker=1.1.10+git20130802-1ubuntu2.5~ppa1)
are meant to contain these additional changes and upgrade together. I
will test them once they are built.

-- 
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