group.of.nepali.translators team mailing list archive

[James Page <james.page@xxxxxxxxxx>]

I think this is a packaging/upstream bug which I appear to have had a go
at before (see #4); however I've not seen this specific symptom before.

** Changed in: charm-hacluster
       Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1727063

Title:
  Pacemaker package upgrades stop but fail to start pacemaker resulting
  in HA outage

Status in OpenStack hacluster charm:
  Invalid
Status in pacemaker package in Ubuntu:
  Triaged
Status in pacemaker source package in Xenial:
  Triaged
Status in pacemaker source package in Zesty:
  Triaged
Status in pacemaker source package in Artful:
  Triaged
Status in pacemaker source package in Bionic:
  Triaged

Bug description:
  We have found on our openstack charm-hacluster implementations that
  the pacemaker .deb packaging along with the upstream pacemaker
  configuration result in pacemaker stopping but not starting upon
  package upgrade (while attended or unattended).

  This was seen on three separate Xenial clouds.  Both Mitaka and Ocata.

  The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2.

  It appears that pacemaker.prerm stops the service using
  "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial.  It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers.  (or rather, they are blank.)

  I have not checked whether this affects trusty environments.

  I'd suggest on systems that use systemd, the pacemaker.postinst script
  should check if the service is enabled and start it with systemctl
  commands rather than using the cross-platform compatible invoke-rc.d
  wrappers.  Or upstream pacemaker should get default start/stop
  entries.

  Our default runlevel on cloud init built images appears to be 5
  (graphical), so at least 5 should be present in /etc/init.d/pacemaker
  LSB init headers under Default-Start:.

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