Multiple units told they are leaders
Bug #1723184 reported by
Jacek Nykis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Joseph Phillips | ||
2.4 |
Fix Released
|
Medium
|
Joseph Phillips | ||
juju-core |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
In my environment I had 5 out of 8 units end up with hook errors.
On closer inspection I noticed that all failed units wrongly thought they were leaders and were trying to "leader-set" which was failing.
Once I run "juju resolved" on all affected units they worked fine.
I could not find anything interesting in the logs.
This is the 2nd bug I noticed recently that affects leadership election so they may be related. The other is bug 1721159.
juju 1.25.13
Ubuntu 14.04.5 LTS
Related branches
lp:~hloeung/ubuntu-repository-cache/i-really-am-the-leader
- Chris Glass: Approve
-
Diff: 14 lines (+4/-0)1 file modifiedhooks/hooks.py (+4/-0)
Changed in juju: | |
status: | Triaged → In Progress |
no longer affects: | juju-core/2.0 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
no longer affects: | juju/2.8 |
To post a comment you must log in.
I have seen kind of the same thing just today, on a fresh 2.2.4 (<24h) model :
2017-10-12 19:28:26 INFO juju-log leader-elected fired. This unit is the new leader: foo/3 CalledProcessEr ror: Command '['leader-set', 'leader_id=foo/3']' returned non-zero exit status 1 uniter. operation runhook.go:107 hook "leader-elected" failed: exit status 1
2017-10-12 19:28:26 DEBUG leader-elected ERROR cannot write leadership settings: cannot write settings: not the leader
[...]
2017-10-12 19:28:26 DEBUG leader-elected subprocess.
2017-10-12 19:28:26 ERROR juju.worker.