I had exactly the same problem yesterday, but I put it down to having probably created the controller with beta2 and trying to kill it with beta3. I also resorted to the nuclear option in the end and deleted everything - I guess I could have been more circumspect and removed the particular parts causing issues, but it wasn't a setup I cared about.
I think you are right that kill-controller ought to do just that, by whatever means necessary. On 3 April 2016 at 14:45, John Meinel <[email protected]> wrote: > I'm not sure what happened, but I can't bootstrap, and I can't > kill-controller to try again. I started out with "failing to get > controller-uuid". I then manually killed the machines, but now I get > "unable to get bootstrap information". > > Clearly there is *some* bootstrap information, or I would be able to "juju > bootstrap", but apparently there isn't enough information so I can't "juju > kill-controller". > > I feel like we're missing something in our implementation. I realize this > is *probably* just version skew, where I was using one of the earlier dev > releases, and then it broke against a new dev release. However, it also > feels like we're missing a more fundamental "kill should make due with the > information it has, and cleanup". "juju destroy-environment --force" was > our old big hammer to wipe the slate clean. But now our attempts at wiping > the state clean all seem to trip up at every turn. The best I've found is > to "rm -rf ~/.local/share/juju" but that, of course, means I lose *all* of > my controllers and my credentials. > > It feels like things like "kill-controller" shouldn't be "allowed" to > fail. Throwing exceptions during cleanup is usually something that isn't > helpful. > > Thoughts? > > John > =:-> > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > > -- Nick Veitch, CDO Documentation Canonical
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
