sts-sponsors team mailing list archive

[Nish Aravamudan <nish.aravamudan@xxxxxxxxxxxxx>]

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 1927) is running...

Add PPA and upgrade corosync:

# add-apt-repository ppa:nacc/lp1740892
# apt-get update; apt-get install corosync

# service corosync status; service pacemaker status
 * corosync is running
pacemakerd is stopped

So what is in my PPA is not yet a fix and I think I see why:

Preparing to unpack .../corosync_2.3.3-1ubuntu4.1~ppa3_amd64.deb ...
 * Stopping corosync daemon corosync                                  
...
Setting up corosync (2.3.3-1ubuntu4.1~ppa3) ...
Installing new version of config file /etc/init.d/corosync ...
 * Restarting corosync daemon corosync                                                                                                                                                                             warning [MAIN  ] Could not lock memory of service to avoid page faults: Cannot allocate memory (12)

So the postinst change is correct and we now restart corosync instead of
start it. However, because the old package's prerm is run, that leads to
a stop of corosync which in turn causes pacemaker to exit. When we run
our updated init-script, it does not detect that pacemaker is running
and so does not restart it.

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

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