destroying a controller with models in error hangs

[Jeff Pihach]

It appears that if you have a model with an application in error you cannot destroy the controller.

To reproduce:
bootstrap and deploy an application to the default model that will fail in some fashion.
run `juju destroy-controller foo --destroy-all-models -y`
It will loop with the message "Waiting on 1 model, 2 machines, 2 applications" potentially forever.
It also doesn't appear to be possible to force destroy the controller.

  :juju destroy-controller aws-us-east-1 --destroy-all-models -y --force
  ERROR option provided but not defined: --force

To actually clean it up I had to `juju destroy-model default --force -y` and then `juju destroy-controller --destroy-all-models -y` It then torn everything down correctly.

What I would expect to happen:
If a model has applications in error (and you want to maintain that you do not tear down things in error) When you try to destroy the controller it should halt with an error message that it will not destroy the controller because of model x and if I'd still like to tear everything down then use --force.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.