Comment 4 for bug 1210054

Thanks, James. lxc-stop is returning false because the machine is already stopped, and juju is (it seems) stopping there because of failure. We can either (a) have juju ignore lxc-stop failure, (b) just have juju run lxc-destroy -f which will implicitly stop the machine if needed (and not manually run lxc-stop), or (c) update lxc-stop to not return failure if the machine was already stopped.

I personally think both (b) and (c) seem reasonable, though someone may object to the lxc-stop change.

Certainly (b) will work around (c), so (b) by itself will fix this.