← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1052449] Re: corosync hangs due to missing pacemaker shutdown scripts

 

I'm marking Precise and Trusty as affected.

The suggested fix is currently implemented by Xenial already:

mcp/pacemaker.in:

...
# Required-Start:       $network corosync
# Should-Start:         $syslog
# Required-Stop:        $network corosync
...


** Also affects: pacemaker (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Also affects: pacemaker (Ubuntu Xenial)
   Importance: Undecided
       Status: New

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

** Changed in: pacemaker (Ubuntu Xenial)
       Status: New => Fix Released

** Changed in: pacemaker (Ubuntu Trusty)
       Status: New => Confirmed

** Changed in: pacemaker (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: pacemaker (Ubuntu)
       Status: Triaged => Fix Released

** Changed in: pacemaker (Ubuntu)
   Importance: High => Undecided

** Changed in: pacemaker (Ubuntu Trusty)
       Status: Confirmed => Triaged

** Changed in: pacemaker (Ubuntu Precise)
       Status: Confirmed => Triaged

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

Title:
  corosync hangs due to missing pacemaker shutdown scripts

Status in pacemaker package in Ubuntu:
  Fix Released
Status in pacemaker source package in Precise:
  Triaged
Status in pacemaker source package in Trusty:
  Triaged
Status in pacemaker source package in Xenial:
  Fix Released

Bug description:
  The pacemaker package installs the right init script but doesn't link
  it to the according runlevels. If corosync is activated and started on
  the system this leads to a hanging shutdown / reboot because corosync
  only ends if pacemaker is stopped beforehand. In addition to this the
  pacemaker daemon has to start after corosync but has to stop before
  corosync.

  A possible solution would be to link the init script accordingly an
  enable it throug /etc/default/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions