Comment 6 for bug 1183309

remove-machine --force already cascades to remove-unit for any units that
were seen as on that machine.
Is that not sufficient for the use case? Is the idea that you might have
multiple units on a machine and only want to clean up one of them?

John
=:->

On Sun, May 4, 2014 at 8:57 PM, Kapil Thangavelu <<email address hidden>
> wrote:

> This is a usability issue, we're making users clean up after juju. if you
> have units in error then lacking --force means manually correcting each
> unit (possibly multiple times) then finally destroying the service... and
> then going back and killing each machine.
>
>
> On Mon, Apr 28, 2014 at 2:03 PM, John A Meinel <<email address hidden>
> >wrote:
>
> > Per the discussion on lp:1089289 destroy-service --force is not going to
> > be implemented because destroy-unit --force is not going to be
> implemented.
> > We have destroy-machine --force for how to clean things up when a unit
> > agent is failing to progress, and we have regular "juju destroy-service"
> > which should cascade to kill all the units already.
> >
> > ** Changed in: juju-core
> > Status: Triaged => Won't Fix
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1183309
> >
> > Title:
> > destroy-service should have a force option
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/juju-core/+bug/1183309/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1183309
>
> Title:
> destroy-service should have a force option
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1183309/+subscriptions
>