sts-sponsors team mailing list archive

[Victor Tapia <victor.tapia@xxxxxxxxxxxxx>]

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 || exit $?
fi
# End automatically added section

- After the change, the same file will stop only for removal:

# Automatically added by dh_installinit
if ([ -x "/etc/init.d/corosync" ] || [ -e "/etc/init/corosync.conf" ]) && \
   [ "$1" = remove ]; then
        invoke-rc.d corosync stop || exit $?
fi
# End automatically added section

I still prefer this fix instead of changing how pacemaker and corosync
unit files relate to each other.


2. Trusty:

- corosync and pacemaker use sysv scripts (however, upstart files are present in the source for both coro&pace). 
- Switching pacemaker to upstart with the respawn stanza should be enough to fix this issue.


[1]
override_dh_installinit:
        dh_installinit --restart-after-upgrade

[2] https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-
of-installation-or-upgrade

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