remove-application does not remove failed application
Bug #1642868 reported by
Stuart Bishop
This bug report is a duplicate of:
Bug #1643430: Unassigned units in an error state cannot be removed.
Edit
Remove
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
remove-application does not remove units in an error state, despite this being a very common thing people want to do. Instead, the operator has to 'resolve' the error state several times until the unit finally disappears.
As the operator explicitly stated that the application is being torn down, I think it is safe to ignore the initial error state on the units and just tear them down without running hooks.
What might be considered less safe is if the error state occurred during teardown (eg. a failed stop hook). This could require an explicit 'resolve' from the operator to ensure they are aware of the problem.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.2.0 |
To post a comment you must log in.
Using 2.1-beta2 it appears that it's impossible to delete units in error. Because Juju keeps retrying hooks even if you resolve the error after destroying it, it gets stuck in a loop and the only way is to `juju remove-machine 0 --force`.