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

2018-01-30 Thread Nish Aravamudan
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

[Sts-sponsors] [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

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

2018-01-18 Thread Nish Aravamudan
Xenial MPs updated and packages uploaded to PPA: corosync - 2.3.5-3ubuntu2.1~ppa2 pacemaker - 1.1.14-2ubuntu1.4~ppa2 Bionic will have to wait til tomorrow. -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

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

2018-01-18 Thread 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

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

2018-01-17 Thread Nish Aravamudan
Testing on Trusty: # apt-get install corosync pacemaker # Make corosync start at boot # sed -i 's/no/yes/' /etc/default/corosync # Make pacemaker start at boot # update-rc.d pacemaker defaults # reboot # service corosync status; service pacemaker status * corosync is running pacemakerd (pid

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

2018-01-17 Thread Nish Aravamudan
Ok, I've put up MPs for Trusty (just corosync) and Xenial (corosync and pacemaker). I think that's correct, and the underlying bug here (package upgrade of corosync does not lead to pacemaker restarting) should be resolved in both cases [1) in c#33]. Additionally, case 2) in c#33 is resolved in

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

2018-01-16 Thread Nish Aravamudan
Sorry for the long-winded, and delayed update to the bug! Here's my TL;DR: 1) We want the postinst of corosync to be created with dh_installinit --restart-on-upgrade, which is the default in compat levels <= 10. 2) We want the init scripts (of whatever type) to restart pacemaker, if they

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

2018-01-16 Thread Nish Aravamudan
My findings from today: 1) This situation has always existed on Trusty, afaict. Removing the regression related tag. 2) There are 24 possible combinations to consider (some are by definition green already, but I'm including them for completeness; and some are not achievable) for each release: