** 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
** 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
For this particular bug, it seems we have no description on why corosync
was taking too long to start, just that it took too long and all the
workaround made to pacemaker initialization and charm handling. With
that, I'm marking corosync as incomplete for now, that I'm gathering all
work to be
Hi,
Corey mentioned 1.1.15 might be fixed a while ago.
You have all the context - is it?
So would that be for corosync:
- Yakkety/Zesty Fixed
- Xenial SRU needed
Or is this totally solved by the charm changes you submitted.
Or ...
TL;DR please help me to understand what might be left on the
** 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
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654403
Title:
Race condition in hacluster charm that leaves pacemaker down
** 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
Milestone: None => 17.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654403
Title:
Race condition in hacluster charm that leaves pacemaker down
To manage
** 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 =>
** 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 =>
** Changed in: hacluster (Juju Charms Collection)
Status: Triaged => Fix Committed
** Changed in: hacluster (Juju Charms Collection)
Assignee: (unassigned) => David Ames (thedac)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Additional information from the charm:
Without cluster_count set to NUM_UNITS a race occurs where the relation
to the last hacluster node is not yet set leading to the attempt to
startup corosync and pacemaker with only n-1/n nodes.
The last node only has one relationship it is aware of yet when
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654403
Title:
Race condition in hacluster charm that leaves pacemaker down
To manage notifications about this bug go to:
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
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"
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"
Corey,
This is Mitaka on Xenial. I suspect that the package remains the same on
Xenial for the other OpenStack releases. I'll try and confirm this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654403
Title:
Root cause:
1) When corosync is restarted it may take up to a minute for it to
finish setting up.
2) The systemd timeout value is exceeded.
Jan 10 18:57:49 juju-39e3e2-percona-3 systemd[1]: Failed to start Corosync
Cluster Engine.
Jan 10 18:57:49 juju-39e3e2-percona-3 systemd[1]:
21 matches
Mail list logo
