remove-application does not remove failed application

Bug #1642868 reported by Stuart Bishop
26
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
Revision history for this message
Jeff Pihach (hatch) wrote :

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`.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

This has been addressed in 2.1-rc1.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.