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 Ubuntu
Server, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1052449
Title:
corosync hangs due to missing pacemaker shutdown scripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1052449/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
