sts-sponsors team mailing list archive

[Nish Aravamudan <nish.aravamudan@xxxxxxxxxxxxx>]

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 following scenarios:

(to level-set)
X -> B [should be broken]

X -> B + PPA [should work]

A -> B [may or may not be broken, because there is not a corosync
version change]

A -> B + PPA [should work]

as well as the prior cases of fresh install in B and reinstall in B.

Additionally, we should be able to test starting/stopping/restarting of
corosync in B successfully doing the same state to pacemaker.

Presuming these tests pass and the Canonical Server Team reviews and
approves them, I will upload them this week.

Eric & co. at that point, I'm wondering if perhaps your team can pick up
the SRUs to X, A and T? I think X and A will take the same changes. As
we discussed, we would do the minimum required for the older releases,
as in my MPs already up. The only thing currently missing is a debconf
note prompt, I think, that says pacemaker will have been stopped by the
corosync upgrade and will need to be manually restarted.

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892

Title:
  corosync upgrade on 2018-01-02 caused pacemaker to fail

Status in OpenStack hacluster charm:
  Invalid
Status in corosync package in Ubuntu:
  In Progress
Status in corosync source package in Trusty:
  Confirmed
Status in corosync source package in Xenial:
  Confirmed
Status in corosync source package in Artful:
  Confirmed
Status in corosync source package in Bionic:
  In Progress
Status in corosync package in Debian:
  New

Bug description:
  During upgrades on 2018-01-02, corosync and it's libs were upgraded:

  (from a trusty/mitaka cloud)

  Upgrade: libcmap4:amd64 (2.3.3-1ubuntu3, 2.3.3-1ubuntu4),
  corosync:amd64 (2.3.3-1ubuntu3, 2.3.3-1ubuntu4), libcfg6:amd64
  (2.3.3-1ubuntu3, 2.3.3-1ubuntu4), libcpg4:amd64 (2.3.3-1ubuntu3,
  2.3.3-1ubuntu4), libquorum5:amd64 (2.3.3-1ubuntu3, 2.3.3-1ubuntu4),
  libcorosync-common4:amd64 (2.3.3-1ubuntu3, 2.3.3-1ubuntu4),
  libsam4:amd64 (2.3.3-1ubuntu3, 2.3.3-1ubuntu4), libvotequorum6:amd64
  (2.3.3-1ubuntu3, 2.3.3-1ubuntu4), libtotem-pg5:amd64 (2.3.3-1ubuntu3,
  2.3.3-1ubuntu4)

  During this process, it appears that pacemaker service is restarted
  and it errors:

  syslog:Jan  2 16:09:33 juju-machine-0-lxc-4 pacemakerd[1994]:   notice: crm_update_peer_state: pcmk_quorum_notification: Node juju-machine-1-lxc-3[1001] - state is now lost (was member)
  syslog:Jan  2 16:09:34 juju-machine-0-lxc-4 pacemakerd[1994]:   notice: crm_update_peer_state: pcmk_quorum_notification: Node juju-machine-1-lxc-3[1001] - state is now member (was lost)
  syslog:Jan  2 16:14:32 juju-machine-0-lxc-4 pacemakerd[1994]:    error: cfg_connection_destroy: Connection destroyed
  syslog:Jan  2 16:14:32 juju-machine-0-lxc-4 pacemakerd[1994]:   notice: pcmk_shutdown_worker: Shuting down Pacemaker
  syslog:Jan  2 16:14:32 juju-machine-0-lxc-4 pacemakerd[1994]:   notice: stop_child: Stopping crmd: Sent -15 to process 2050
  syslog:Jan  2 16:14:32 juju-machine-0-lxc-4 pacemakerd[1994]:    error: pcmk_cpg_dispatch: Connection to the CPG API failed: Library error (2)
  syslog:Jan  2 16:14:32 juju-machine-0-lxc-4 pacemakerd[1994]:    error: mcp_cpg_destroy: Connection destroyed

  
  Also affected xenial/ocata

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions