units stuck in model after failed deploy
Bug #1728721 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Tried to deploy a charm that uses juju storage to a lxd on a aws instance, got an error that storage wasn't supported, then the units decided to stick around.
To reproduce, just deploy a charm that uses storage to lxd on aws instance using aws provider and the beta juju snap and you should hit this.
e.g
juju add-machine # gets machine 0
juju deploy cs:~jamesbeedy/
juju status --format yaml http://
juju status http://
Changed in juju: | |
milestone: | 2.4-beta1 → none |
To post a comment you must log in.
If a unit goes into an error state, it won't be automatically removed. I don't think remove-unit likes to remove units in error either, and sadly there's no --force option. I think we do need to consider supporting "remove-unit --force" to allow such situations to be clean up.