destroy-service should have a force option
Bug #1183309 reported by
Kapil Thangavelu
This bug affects 14 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
much the same as Bug #1089289 except as option to destroy-service, so that all units of the service are forced to destroy instead of having the user manually push them through a workflow only to delete them. This seems to trip up users regularly.
Changed in juju-core: | |
importance: | Undecided → Low |
status: | New → Confirmed |
tags: | added: ui workflow |
Changed in juju-core: | |
importance: | Medium → Low |
tags: | added: destroy-service |
Changed in juju-core: | |
importance: | Low → High |
Changed in juju-core: | |
status: | Won't Fix → Triaged |
milestone: | none → next-stable |
tags: | added: usability |
Changed in juju-core: | |
status: | In Progress → Incomplete |
Changed in juju-core: | |
status: | Incomplete → Triaged |
Changed in juju-core: | |
assignee: | Casey Marshall (cmars) → nobody |
Changed in juju-core: | |
importance: | High → Medium |
milestone: | next-stable → none |
To post a comment you must log in.
I want this for writing reliable functional tests. A broken hook will cause the test suite to hang.