Destroyed leader, new leader not elected.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Dave Cheney | ||
juju-core |
Fix Released
|
High
|
Dave Cheney | ||
1.25 |
Fix Released
|
High
|
Dave Cheney |
Bug Description
I've been trying to track down a test failure in lp:~stub/charms/trusty/postgresql/rewrite, where the failover tests consistently fail on the Ecosystem Team's Jenkins (including the local provider) but always pass locally using the local provider.
I believe I have narrowed it down to Juju not promoting a surviving unit to leader after the leader is destroyed.
In the attached logs, the failing test starts around 2015-10-29 04:08:10.
First, a new unit is added to the PostgreSQL service. This works just fine.
At 2015-10-29 04:10:12, the leader (postgresql/0) is destroyed. This kicks of many, many hooks starting with leader-
By 2015-10-29 04:10:36 things are winding down, where you can see the final replication-
At 2015-10-29 04:10:42, the stop hook is run on postgresql/0, successfully.
No further hooks run for the next 6 minutes. After this, the test suite gives up and things are torn down for the next set of tests.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-core: | |
milestone: | none → 1.26.0 |
tags: | added: bug-squad leadership |
Changed in juju-core: | |
milestone: | 1.26.0 → 2.0-alpha2 |
Changed in juju-core: | |
assignee: | nobody → William Reade (fwereade) |
Changed in juju-core: | |
assignee: | William Reade (fwereade) → Dave Cheney (dave-cheney) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-alpha2 → none |
milestone: | none → 2.0-alpha2 |
Changed in juju-core: | |
assignee: | nobody → Dave Cheney (dave-cheney) |
importance: | Undecided → High |
status: | New → Fix Released |
The attached log came from the lxc run at http:// reports. vapour. ws/charm- test-details/ charm-bundle- test-parent- 3201
I believe the same failure is happening with all the providers (same test failure - service gives up waiting for a master to appear), but have not trawled through their logs to confirm.