Service with just one unit left which doesn't think it's the leader
Bug #1488166 reported by
Adam Collard
This bug report is a duplicate of:
Bug #1511659: Destroyed leader, new leader not elected..
Edit
Remove
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Triaged
|
High
|
William Reade |
Bug Description
I'm not sure of exact steps to reproduce this, but broadly it was
1. juju deploy foo
2. // Oops, hit an error in install hook because I forgot some config
3. juju set foo bar=baz
4. juju retry --resolved foo/0
5. // Oops that still didn't work
6. juju destroy-unit foo/0
7. juju set foo bar=baz
8. juju add-unit foo --to lxc:0
9. // WTH, my service is behaving weirdly
10. juju run --service foo is-leader
Output:
False
Expected:
True
$ juju version
1.24.5-vivid-amd64
MAAS provider using 1.8.1
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.25.0 |
Changed in juju-core: | |
milestone: | 1.25-alpha1 → 1.25-beta1 |
Changed in juju-core: | |
assignee: | nobody → William Reade (fwereade) |
milestone: | 1.25-beta1 → 1.25-beta2 |
Changed in juju-core: | |
status: | New → Triaged |
Changed in juju-core: | |
status: | Triaged → In Progress |
description: | updated |
Changed in juju-core: | |
milestone: | 1.25-beta2 → 1.25.1 |
Changed in juju-core: | |
milestone: | 1.25.1 → 1.25.2 |
Changed in juju-core: | |
milestone: | 1.25.2 → 1.25.3 |
Changed in juju-core: | |
status: | New → Triaged |
tags: | added: kanban-cross-team |
tags: | removed: kanban-cross-team |
To post a comment you must log in.
Did it stay false forever, or did it get elected within 60s? Would love to see logs if you can repro...