** Also affects: corosync (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: corosync (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a
** Changed in: charm-hacluster
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1654403
Title:
Race condition in hacluster charm that
** Changed in: charm-hacluster
Milestone: None => 17.02
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1654403
Title:
Race condition in hacluster charm that leaves pacemaker
** Changed in: charm-hacluster
Importance: Undecided => High
** Changed in: charm-hacluster
Status: New => Fix Committed
** Changed in: charm-hacluster
Assignee: (unassigned) => David Ames (thedac)
** Changed in: hacluster (Juju Charms Collection)
Status: Fix Committed =>
David, you could try adding "Restart=on-failure" back to the init file
as a test. If it works, we could look into backporting that to xenial,
however I'm hesitant to do that until we know better why they dropped
the restart bits in the first place.
--
You received this bug notification because
This may have been fixed as of the 1.1.15-1 version of the pacemaker
package. Prior to commit 071796e, "Restart=on-failure" was patched out.
I've attached the diff of the commit that reverted that.
** Patch added: "pacemaker-071796e.diff"
David, what release of ubuntu/openstack does this affect? I'd like to
see if we can get a package update in a PPA for you to test with.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
