Leader role not transferred when the inital leader goes offline
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Joseph Phillips |
Bug Description
# How to reproduce
1) create a cluster of 3 units:
$ juju deploy ./lxd_ubuntu-
$ juju add-unit lxd --to 97
2) take the leader (lxd/78) offline
$ juju ssh lxd/78
$ sudo halt -p
3) wait a little for lxd/78 to loose it's leader status
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
test overlord maas/default 2.9.15 unsupported 19:06:21Z
App Version Status Scale Charm Store Channel Rev OS Message
lxd active 2/3 lxd local 30 ubuntu
Unit Workload Agent Machine Public address Ports Message
lxd/78 unknown lost 95 2602:fc62:
lxd/79 active idle 96 2602:fc62:
lxd/80 active idle 97 2602:fc62:
Machine State DNS Inst id Series AZ Message
95 down 2602:fc62:
96 started 2602:fc62:
97 started 2602:fc62:
99 started 2602:fc62:
101 started 2602:fc62:
102 started 2602:fc62:
104 started 2602:fc62:
105 started 2602:fc62:
106 started 2602:fc62:
107 started 2602:fc62:
108 started 2602:fc62:
109 started 2602:fc62:
110 started 2602:fc62:
111 started 2602:fc62:
112 started 2602:fc62:
After some time, one would expect a new leader to be elected but that is not the case.
# Additional information
$ juju --version
2.9.16-ubuntu-amd64
tags: | added: canonical-is-upgrades |
tags: | added: leadership |
Changed in juju: | |
status: | Fix Committed → Fix Released |
This is addressed by: /github. com/juju/ juju/pull/ 13429
https:/