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. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1210054 Title: juju terminate-machine with local provider doesn't destroy machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1210054/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
