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

** Changed in: corosync (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage

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

This bug was fixed in the package pacemaker - 1.1.14-2ubuntu1.4 --- pacemaker (1.1.14-2ubuntu1.4) xenial; urgency=high * Properly restart corosync and pacemaker together (LP: #1740892) - d/pacemaker.preinst: flag corosync to restart pacemaker on upgrade. -- Eric

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

This bug was fixed in the package pacemaker - 1.1.17+really1.1.16-1ubuntu2 --- pacemaker (1.1.17+really1.1.16-1ubuntu2) artful; urgency=medium * Rebuilding with a version greater than 1.1.17: - pacemaker 1.1.17 was pushed to Artful at one point and then got deleted. pacemaker

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

This bug was fixed in the package corosync - 2.3.5-3ubuntu2.1 --- corosync (2.3.5-3ubuntu2.1) xenial; urgency=high * Properly restart corosync and pacemaker together (LP: #1740892) - d/rules: pass --restart-after-upgrade to dh_installinit - d/control: indicate this version

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

This bug was fixed in the package corosync - 2.4.2-3ubuntu0.17.10.1 --- corosync (2.4.2-3ubuntu0.17.10.1) artful; urgency=high * Properly restart corosync and pacemaker together (LP: #1740892) - d/rules: pass --restart-after-upgrade to dh_installinit - d/control: indicate

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

[VERIFICATION ARTFUL] Upgrade went well, and have restarted pacemaker on a corosync installation as it should. # systemctl status corosync Active: active (running) since Thu 2018-03-01 15:18:08 UTC; 2min 37s ago Main PID: 2366 (corosync) systemctl status pacemaker Active: active

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

** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to

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

[VERIFICATION XENIAL] * == corosync upgrade (with pacemaker installed) == # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial # dpkg -l ii corosync 2.3.5-3ubuntu2 amd64 cluster engine daemon

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

Hello Drew, or anyone else affected, Accepted pacemaker into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pacemaker/1.1.17+really1.1.16-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new

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

I had to re-uploader pacemaker for artful. at one point someone tried to push 1.1.17 into Artful and it then got deleted, which leave me with no other choice but to re-upload with a version greater than 1.1.17 for the SRU machinery to accept the changes. -- You received this bug notification

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

Hello Drew, or anyone else affected, Accepted corosync into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/corosync/2.4.2-3ubuntu0.17.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

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

** Description changed: [Impact] When corosync and pacemaker are both installed, a corosync upgrade caused pacemaker to fail. pacemaker will need to be restarted manually to work again, it won't recover by itself. [Test Case] 1) Have corosync (< 2.3.5-3ubuntu2) and pacemaker

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

Uploaded for Xenial and Artful, it is now waiting in the upload queue for SRU verification team approval. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02

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

[Artful (pre-sru)] # dpkg -l | egrep "corosync|pacemaker" ii corosync 2.4.2-3build1 amd64cluster engine daemon and utilities ii crmsh 2.3.2-1

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

I'll resume the SRU and hopefully upload everything next Monday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage

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

Was able to build fine using (optional) Standard symbol tags optional A symbol marked as optional can disappear from the library at any time and that will never cause dpkg-gensymbols to fail. However, disappeared optional symbols will continuously appear as MISSING in the

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

another quick update base on a discussion between nacc/slangasek and myself : ... slangasek: fair, above patch results in https://paste.ubuntu.com/p/hb68G8rpMw/ nacc: those are pretty clearly internal symbols which are not part of the ABI and you should just mark them (optional) instead of

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

Quick update The corosync/pacemaker SRU is on hold for now until the FBTFS situation is fix for Artful. As mentioned above in comment #58 based on the build log error I had and the debbug #869986, it is related to some libqb header issues. Server team will have a look at this, and I'll

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

I did some preliminary investigation on the second build failing for pacemaker in Artful. And it seems to be related to a binutils/libqb issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869986 https://bugzilla.redhat.com/show_bug.cgi?id=1477354

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

I think the chance we have users running pacemaker on Artful can be consider low and will become even more lower with the release of Bionic in ~2months. Bionic already contain the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

Before nacc and I spend time on fixing Artful FTBFS situation in order to SRU this fix... I'll ask the SRU team for guidance if, base on Artful current information/situation, it is reasonable to skip Artful and focus on Xenial. -- You received this bug notification because you are a member of

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

Based upon discussion, we will not be fixing this in Trusty. Updating the SysV scripts to be more error-proof is itself error-prone. Additionally, corosync on Trusty has not received significant updates, and this update itself would lead to at least an additional outage (in order to put the fix

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

Based upon discussion, we will not be fixing this in Trusty. Updating the SysV scripts to be more error-proof is itself error-prone. Additionally, corosync on Trusty has not received significant updates, and this update itself would lead to at least an additional outage (in order to put the fix

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

Forgot the mentioned that It still fails to build, but it fails differently now than before applying debian commit "a7476dd96e79197f65acf0f049f75ce8e8f9e801" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

It still FTBFS with the above Debian candidate commit ^ - Eric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage

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

I *think* this debian commit could possibly be a good candidate to fix Artful FTBFS situation. --- $ git show a7476dd9 commit a7476dd96e79197f65acf0f049f75ce8e8f9e801 Author: Jan Pokorny Date: Thu Feb 2 14:51:46 2017 +0100 Fix: crm_mon: protect against

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

[ARTFUL pacemaker - note ] pacemaker package doesn't build (doesn't build as is without any changes) in Artful. I suspect the package has been first build in Zesty and then simply copied to Artful when the release was first created (without going through the build farm again). Additionally, no

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

** Description changed: [Impact] When corosync and pacemaker are both installed, a corosync upgrade caused pacemaker to fail. pacemaker will need to be restarted manually to work again, it won't recover by itself. [Test Case] 1) Have corosync (< 2.3.5-3ubuntu2) and pacemaker

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

** Description changed: + [Impact] + + When corosync and pacemaker are both installed, a corosync upgrade + caused pacemaker to fail. pacemaker will need to be restarted manually + to work again, it won't recover by itself. + + [Test Case] + + 1) Have corosync (< 2.3.5-3ubuntu2) and pacemaker

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

[XENIAL (pre-SRU)] == BEFORE UPGRADE == # dpkg -l | egrep "corosync|pacemaker" ii corosync 2.3.5-3ubuntu2 amd64cluster engine daemon and utilities ii crmsh2.2.0-1 amd64

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

** Also affects: pacemaker (Ubuntu) Importance: Undecided Status: New ** Changed in: pacemaker (Ubuntu) Status: New => In Progress ** Changed in: pacemaker (Ubuntu) Status: In Progress => Fix Released ** Changed in: pacemaker (Ubuntu) Assignee: (unassigned) => Nish

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

** Tags added: id-5a53cc961fb7361dbac726f8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage notifications about this

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

I'll proceed with the SRU next week. As per my discussion with server team, we will fix Xenial and Artful but we won't fix Trusty. ** Changed in: corosync (Ubuntu Artful) Assignee: Nish Aravamudan (nacc) => Eric Desrochers (slashd) ** Changed in: corosync (Ubuntu Xenial) Assignee:

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

This bug was fixed in the package corosync - 2.4.2-3ubuntu1 --- corosync (2.4.2-3ubuntu1) bionic; urgency=medium * Properly restart corosync and pacemaker together (LP: #1740892) - d/rules: pass --restart-after-upgrade to dh_installinit - d/control: indicate this version

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

I have uploaded the fixes today to Bionic. I will update the bug once they are migrated, but the SRUs should be startable 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

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

I have uploaded the fixes today to Bionic. I will update the bug once they are migrated, but the SRUs should be startable now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync

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

Hello I'm fixing the other pacemaker/glib bug[1]. but it is blocked by this issue. It would be good if there is good news for this issue i hope. Thanks. [1] https://bugs.launchpad.net/bugs/1316970 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

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

** Changed in: corosync (Ubuntu Artful) Assignee: Eric Desrochers (slashd) => Nish Aravamudan (nacc) ** Changed in: corosync (Ubuntu Xenial) Assignee: Eric Desrochers (slashd) => Nish Aravamudan (nacc) ** Changed in: corosync (Ubuntu Trusty) Assignee: Victor Tapia (vtapia) => Nish

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

I did some cursory testing yesterday (I still need to think about how to do a X -> B upgrade w/ a PPA) of B -> B updates. pacemaker stays running as expected. I am checking (via the MP, a comment recently) if it's possible to minimize our changes even more in 18.04. -- You received this bug

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

I did some cursory testing yesterday (I still need to think about how to do a X -> B upgrade w/ a PPA) of B -> B updates. pacemaker stays running as expected. I am checking (via the MP, a comment recently) if it's possible to minimize our changes even more in 18.04. -- You received this bug

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

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

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

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

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336063 ** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336879 ** Merge proposal linked:

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336579 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336508 ** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336509 -- You received this bug notification because you are a member

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

[VERIFICATION for XENIAL] - [UPGRADE SCENARIO] # dpkg -l | egrep "corosync|pacemaker" ii corosync 2.3.5-3ubuntu2 amd64cluster engine daemon and utilities ii crmsh

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

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.

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

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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title:

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

@slashd, @vtapia: I would appreciate additional testing and I will work on the bionic uploads on Monday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02

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

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

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

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

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

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

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

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

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

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 Ubuntu Server Team, which is subscribed to corosync in Ubuntu.

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

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 Ubuntu Bugs, which is subscribed to Ubuntu.

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336338 ** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336339 -- You received this bug notification because you are a member

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

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

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

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

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336336 ** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336337 -- You received this bug notification because you are a member

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

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

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

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

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

** Changed in: corosync (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage

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

** Bug watch added: Debian Bug tracker #887563 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563 ** Also affects: corosync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563 Importance: Unknown Status: Unknown -- You received this bug notification

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

** Bug watch added: Debian Bug tracker #887563 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563 ** Also affects: corosync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563 Importance: Unknown Status: Unknown -- You received this bug notification

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

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

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

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

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

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

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

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

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336257 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336256 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on

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

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

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

8) On Xenial and on, where we have systemd .service files for both corosync and pacemaker, this is my current understanding (after looking at the .service files and thinking about the Trusty case, as well; some of this is repeats of others' observations): 8a) corosync can be installed configured

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

8) On Xenial and on, where we have systemd .service files for both corosync and pacemaker, this is my current understanding (after looking at the .service files and thinking about the Trusty case, as well; some of this is repeats of others' observations): 8a) corosync can be installed configured

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

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:

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

** Merge proposal linked: https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336185 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on

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

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:

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

** Tags removed: regression-update -- 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

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

** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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

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

** No longer affects: corosync (Ubuntu Zesty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage notifications about

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

** Changed in: corosync (Ubuntu Bionic) Assignee: Eric Desrochers (slashd) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02

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

1. Xenial+: - Overriding dh_installinit[1] would still fail the first time it's upgraded because of the old corosync.prerm file [2], that contains: # Automatically added by dh_installinit if [ -x "/etc/init.d/corosync" ] || [ -e "/etc/init/corosync.conf" ]; then invoke-rc.d corosync stop

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

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: corosync (Ubuntu Zesty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892

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

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: corosync (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892

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

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: corosync (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892

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

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: corosync (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892

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

This issue has been identified as Field Critical. The medium importance assigned to this defect seems counter intuitive to the SLA level assigned. @Eric can you provide some insight into a time frame for a fix. Typically under Critical SLA we expect a dedicated engineer and a fix in a week. --

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

Forgot the link to Pacemaker's FAQ [1] https://wiki.clusterlabs.org/wiki/FAQ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail

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

I was wrong regarding iii) "when corosync is stopped, do not stop pacemaker": Pacemaker can use other applications[1] (e.g. heartbeat) instead of corosync, so this is a property we want to keep. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

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

In my opinion, from the list of desired properties, only the second one is true: i) Corosync can be used on its own, regardless of having pacemaker installed or not. Starting both of them would force to mask pacemaker's unit file under particular scenarios. iii) IIRC, pacemaker requires

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

(maybe actually even /bin/systemctl try-restart pacemaker.service -> restart, if it's running) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused

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

Currently, in bionic: $ systemctl cat pacemaker.service # /lib/systemd/system/pacemaker.service After=corosync.service Requires=corosync.service $ systemctl cat corosync.service Desired properties: i) when corosync is started, attempt to start pacemaker ii) when corosync is restarted, attempt

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

** Also affects: pacemaker (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pacemaker (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: corosync (Ubuntu

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

On Trusty + corosync=2.3.3-1ubuntu1: - Stopping corosync while pacemaker is still running: Jan 9 09:26:55 trusty-corosync corosync[5492]: [MAIN ] Node was shut down by a signal Jan 9 09:26:55 trusty-corosync corosync[5492]: [SERV ] Unloading all Corosync service engines. Jan 9

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

As per nacc's comment it seems like "Wants=" is the recommended way to hook start-up of one unit to the start-up of another unit.[1] [1] - https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Wants= So far I have tested using 2 scenarios (including "Wants=pacemaker.service") and it

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

On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia wrote: > As mentioned by Mario @ #10, stopping corosync while pacemaker runs > throws the same error as the upgrade. Syslog from Xenial + > corosync=2.3.5-3ubuntu1: > > Jan 8 16:24:37 xenial-corosync systemd[1]: Stopping

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

On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia wrote: > As mentioned by Mario @ #10, stopping corosync while pacemaker runs > throws the same error as the upgrade. Syslog from Xenial + > corosync=2.3.5-3ubuntu1: > > Jan 8 16:24:37 xenial-corosync systemd[1]: Stopping

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

On Mon, Jan 8, 2018 at 10:04 AM, Nish Aravamudan wrote: > On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan > wrote: >> On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia >> wrote: >>> As mentioned by Mario @

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

On Mon, Jan 8, 2018 at 10:04 AM, Nish Aravamudan wrote: > On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan > wrote: >> On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia >> wrote: >>> As mentioned by Mario @

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

On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan wrote: > On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia > wrote: >> As mentioned by Mario @ #10, stopping corosync while pacemaker runs >> throws the same error as the upgrade. Syslog from

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

On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan wrote: > On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia > wrote: >> As mentioned by Mario @ #10, stopping corosync while pacemaker runs >> throws the same error as the upgrade. Syslog from

  1   2   >