Relevant bug: https://bugs.launchpad.net/juju-core/+bug/1553059
We should provide a way to clean up controllers without making the user manually edit juju's files. On Mon, Apr 4, 2016 at 7:05 AM, Nate Finch <[email protected]> wrote: > This just happened to me, too. Kill-controller needs to work if at all > possible. That's the whole point. And yes, users may not hit specific > problems, but devs do, and that wastes our time trying to figure out how to > manually clean up the garbage. > > On Mon, Apr 4, 2016 at 8:33 AM Rick Harding <[email protected]> > wrote: > >> On Sun, Apr 3, 2016 at 6:56 PM Andrew Wilkins < >> [email protected]> wrote: >> >>> In a non-beta release we would make sure that the config changes aren't >>> backwards incompatible. >>> >> >> I think this is the key thing. I think that kill-controller is an >> exception to this rule. I think we should always at least give the user the >> ability to remove their stuff and start over with the new alpha/beta/rc >> release. I'd like to ask us to explore making kill-controller an exception >> to this policy and that if tests prove we can't bootstrap on one beta and >> kill with trunk that it's a blocking bug for us. >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
