Comment 3 for bug 1168154

This is a bad user experience from the GUI's perspective.

- In general, if I say "destroy this service," I expect the system to destroy the service and handle any related issues that can be handled mechanically.
- If, for some reason, the destruction can't happen because manual intervention is actually necessary somewhere, I'd expect the "destroy" call to fail with a helpful error message explaining what I need to do to make the destroy succeed.
- If, for some reason, that can't happen either, at the very least I'd expect a hand-holding notification in the GUI: for instance, a message that had to be acknowledged that explained that there was a problem, and what I manually needed to do to resolve it. I suppose the commandline equivalent would be to add something to the juju status output, though that seems problematic in a number of ways.

Simply not finishing a partially completed destruction without any message at all is not a good approach for us.

buildbot failure: the charm expects the pyjuju ppa to be installed, which is where python-shell-toolbox is found for precise. A charm failure. Unfortunately, the charm doesn't have a maintainer any more (my squad used to be the maintainer but we have no need for it any more, and AIUI buildbot is considered to be a very low priority target ATM).