[Ubuntu-ha] [Bug 1525911] [NEW] wrong stop order of corosync and pacemacer

Public bug reported: In case of e reboot, poweroff or "service corosync stop" corosync stops before pacemacer this leads to an inconsistent state. As a communication between the nodes is only possible as long as corosync is running. My current work around is: # fix order of corosync/pacemaker

[Ubuntu-ha] [Bug 1524635] Re: haproxy syslog configuration causes double logging

** Changed in: haproxy (Ubuntu) Importance: Undecided => Medium ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1524635 Title: haproxy syslog

[Ubuntu-ha] [Bug 1525911] Re: wrong stop order of corosync and pacemacer

The start order in the init scripts is not taken into account. -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1525911 Title: wrong stop order of corosync and pacemacer