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

2018-01-19 Thread Nish Aravamudan
On Xenial:

corosync2.3.5-3ubuntu2.1~ppa3
pacemaker   1.1.14-2ubuntu1.4~ppa3

The same 3 test cases as in c#39 alll passed.

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


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

2018-01-19 Thread Nish Aravamudan
4) a case I am not sure what to do with yet (in Trusty or Xenial):
stopping pacemaker and then installing the PPA packages. I'm not sure
how to handle this, really, for 16.04, as the deb-helper scripts don't
seem to have status wrappers and calling systemctl directly does not
apparently work. The end result is that pacemaker will be started in
these cases, which does not seem directly harmful, but I'm not 100% (it
would also presumablly start on next reboot anyways).

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


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

2018-01-19 Thread Nish Aravamudan
After hitting some corner cases with my Trusty packages (and Xenial), I
uploaded new versions:

corosync - 2.3.3-1ubuntu4.1~ppa7

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

And ran the following tests:

1) install corosync and pacemaker, but do not enable either
Upgrade to the PPA packages
No errors, both are still disabled

2) install corosync and pacemaker, enable corosync only
Upgrade to the PPA packages
No errors, corosyc is restarted

3) install corosync and pacemaker, enable both
Upgrade to the PPA packages
No errors, corosync and pacemaker restarted

I'm moving on to update the xenial branches now.

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