Agents are "lost" after terminating a state server in an HA env
Bug #1510651 reported by
Cheryl Jennings
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
juju-core |
Won't Fix
|
High
|
Unassigned | ||
1.25 |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Recreate steps:
1 - Bootstrap (ec2 in my case)
2 - Deploy services and wait for completion
3 - Run ensure-availability -n 3 and wait for completion
4 - Stop the initial state server (machine 0) from the ec2 console
Some services will show as "agent lost".
Killing jujud on "lost" machines will trigger them to reconnect.
Changed in juju-core: | |
importance: | High → Critical |
milestone: | none → 1.25.1 |
tags: | added: bug-squad ensure-availability |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
assignee: | James Tunnicliffe (dooferlad) → nobody |
Changed in juju-core: | |
assignee: | nobody → Wayne Witzel III (wwitzel3) |
Changed in juju-core: | |
milestone: | 1.25.1 → 1.25.2 |
Changed in juju-core: | |
assignee: | Wayne Witzel III (wwitzel3) → Tim Penhey (thumper) |
Changed in juju-core: | |
milestone: | 1.25.2 → 1.25.3 |
Changed in juju-core: | |
milestone: | 1.25.3 → 2.0-alpha1 |
Changed in juju-core: | |
milestone: | 2.0-alpha1 → 2.0-alpha2 |
Changed in juju-core: | |
assignee: | Tim Penhey (thumper) → nobody |
Changed in juju-core: | |
status: | In Progress → Triaged |
milestone: | 2.0-alpha2 → 2.0-alpha3 |
Changed in juju-core: | |
milestone: | 2.0-alpha3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → none |
importance: | Critical → High |
tags: | added: canonical-bootstack |
affects: | juju-core → juju |
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
milestone: | none → 2.0-beta18 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Also, even though machine 0 is stopped, it still shows as "started" in `juju status`