leadership flapping on units of same application across models
Bug #1832424 reported by
Christian Muirhead
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Christian Muirhead | ||
| 2.5 |
Fix Released
|
Undecided
|
Unassigned | ||
| 2.6 |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
If you have multiple units of an application deployed in multiple models in a controller, `juju status` shows the leadership of those applications changing frequently, even though the lease log and the unit status history doesn't show leadership changes.
| Changed in juju: | |
| milestone: | none → 2.5.8 |
| milestone: | 2.5.8 → none |
Revision history for this message
| Christian Muirhead (2-xtian) wrote | #1 |
Revision history for this message
| Christian Muirhead (2-xtian) wrote | #2 |
Revision history for this message
| Christian Muirhead (2-xtian) wrote | #3 |
| Changed in juju: | |
| milestone: | none → 2.7-beta1 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This turned out to be caused by a missing filter in the lease manager, so if an application was in multiple models the the holder would be overwritten for each one and the final leader reported would be whichever was seen last. Since this was coming from a map where the order is nondeterministic the leader would change seemingly at random.