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

[Nish Aravamudan]

I tested the versions mentioned in the last comment (with one syntax
fix) and the upgrade path successfully worked! I need to test more
corner-cases and would appreciate help with that (e.g., corosync only
installed, installing pacemaker separately, etc)

The MPs have been updated and I'm building packages that are source-
identical to the MPs as

corosync - 2.3.3-1ubuntu4.1~ppa6

pacemaker - 1.1.10+git20130802-1ubuntu2.5~ppa3

The reason for the repeated version bumps is these packages now have
inter-related versioning.

I will try and do a similar set of MPs for xenial and bionic first thing
tomorrow, if not later today.

** Merge proposal unlinked:
   https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336185

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