ensure-availability not safe from adding 7+ nodes, can't remove stale ones
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
High
|
Unassigned |
Bug Description
I wanted to enable juju-high-
However, while juju was setting up additional state servers I run 'ensure-
I can run 'ensure-
At the end I ended up with 12 machines - three of them were in 'has-vote' status, two of them are in 'no-vote' status, and the rest don't have state-server-
Running 'juju ensure-
As I have a customer who accidentally ended up in this situation I'd like to know if there is a way to remove 'non-voting' machines? (Even if it includes altering the juju's mongodb database).
I have tested this, against openstack provider (http://
It seems that juju should prevent running 'ensure-
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Just an update, as I managed to 'clean' juju status from 'obsolete' machines.
Once I deleted non-voting machines with 'nova delete', and waited for some time, I run 'juju ensure- availability' again. Juju then 'removed' the machines from 'state- server- member- state' (group? option?). After that I used 'juju remove-machine --force' to get rid of those machines.