Cannot terminate/remove broken state server after ensure-availability
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Incomplete
|
Undecided
|
Unassigned | ||
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
[Environment]
Trusty 14.04
juju-core 1.20.11-
ii maas-cli 1.5.4+bzr2294-
ii maas-cluster-
ii maas-common 1.5.4+bzr2294-
ii maas-dhcp 1.5.4+bzr2294-
ii maas-dns 1.5.4+bzr2294-
ii maas-region-
ii maas-region-
[Description]
$ juju ensure-availability --constraints 'tags=bootstrap" -n 5
One of the node fails to bootstrap because there are no matching tags are availables:
"85":
agent-state-info: 'cannot run instances: gomaasapi: got error back from server:
409 CONFLICT (No matching node is available.)'
instance-id: pending
series: trusty
state-server-
This is a totally valid and possible scenario on which one of the requested state servers fails.
At this point 3 of 5 nodes are already available as state servers, but if you try to remove/terminate the machine 85, even by forcing is not possible to remove this machine from the
$ juju terminate-machine 85 --force
ERROR no machines were destroyed: machine 85 is required by the environment
| tags: | added: destroy-machine ensure-availability |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: |
added: sts removed: cts |
| tags: | added: sts-needs-review |
| tags: | removed: sts-needs-review |
| tags: | added: jujuqa |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| status: | New → Incomplete |
| tags: | added: eda |
| David (dberardozzi) wrote | #2 |
| Anastasia (anastasia-macmood) wrote | #3 |
@Jorge,
You have updated the bug :D
Does it mean that you have a reproducible scenario for Juju 2.x? Could you please share it?
It might be worthwhile re-wording the bug with Juju 2.x terminology for clarity \o/