I agree, unregister exists to say "don't try to clean anything up, just
record that everything is gone". While "kill-controller" assumes there
should be something to clean up.
On Wed, Aug 29, 2018 at 3:33 AM, Tim Penhey <email address hidden>
wrote:
> I'm with Rick on this one. This is why we created the unregister
> command.
>
> As mentioned, the problem could be intermittent, or just a weird
> failure. Removing information about the controller when we hit problems
> is likely to cause more problems than it fixes.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1789443
>
> Title:
> juju kill-controller fails when no connection to lxd remote provider
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1789443/+subscriptions
>
I agree, unregister exists to say "don't try to clean anything up, just
record that everything is gone". While "kill-controller" assumes there
should be something to clean up.
On Wed, Aug 29, 2018 at 3:33 AM, Tim Penhey <email address hidden>
wrote:
> I'm with Rick on this one. This is why we created the unregister /bugs.launchpad .net/bugs/ 1789443 /bugs.launchpad .net/juju/ +bug/1789443/ +subscriptions
> command.
>
> As mentioned, the problem could be intermittent, or just a weird
> failure. Removing information about the controller when we hit problems
> is likely to cause more problems than it fixes.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> juju kill-controller fails when no connection to lxd remote provider
>
> To manage notifications about this bug go to:
> https:/
>