cluster leader changed mid-sync

Bug #1727664 reported by Alvaro Uria
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Swift Proxy Charm
Expired
Undecided
Unassigned

Bug Description

Ubuntu Xenial, OpenStack Charms 17.02.

swift-proxy/0 as juju leader, while s-p/{1,13} as non juju leaders.

Juju leader goes into error state because it claims that the cluster leader has changed mid-sync:
http://pastebin.ubuntu.com/25822184/

Workaround:
1) stop the leader (jujud-unit-swift-proxy-0)
2) wait until the leader moves to a different unit (ie. to swift-proxy/1)
3) start jujud-unit-swift-proxy-0

Revision history for this message
Alvaro Uria (aluria) wrote :

As a collateral issue, swift-proxy/0 juju unit stopped swift-proxy service. Such unit had the VIP.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

As this is over a year old, and lots of changes have been made, I'm setting to incomplete to see if it's still an issue. If not, then it will expire.

Changed in charm-swift-proxy:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack swift-proxy charm because there has been no activity for 60 days.]

Changed in charm-swift-proxy:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.