Another relevant bug: https://bugs.launchpad.net/juju-core/+bug/1566426
Maybe kill-controller tries to destroy through the API, but has a time out if things get "stuck" where it will fall back to the provider. I was joking when I suggested yesterday in IRC that we should bring back --force for kill-controller, but maybe we need it (or at least a timeout). On Wed, Apr 6, 2016 at 7:53 AM, Nate Finch <[email protected]> wrote: > Oh I see. Yes, I agree that we should always try the right way first and > only use the provider if necessary (especially if using the provider leaves > garbage around). > > It seems like there's no reason why we couldn't make a --force flag do it > that way in 2.0 (aside from time constraints). > > On Wed, Apr 6, 2016 at 10:48 AM Aaron Bentley <[email protected]> > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 2016-04-06 10:45 AM, Nate Finch wrote: >> > Wait, didn't destroy-environment --force fall back to the provider? >> > I thought that was the whole point of --force >> >> No, it didn't fall back. It uses the provider unconditionally, >> without trying a normal destroy-controller first. >> >> Aaron >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2 >> >> iQEcBAEBCAAGBQJXBSG5AAoJEK84cMOcf+9hzSQIAJ/vNKIa1/TnDSyvC2U9ApzW >> TAEvSqaEUw0ZL2dl2tiNKTp3JPzcnCR4VKrBIsh1xi0hB1UNtJR+IW4O46gRI6ok >> ZvA1cAvoJvRdmqf1ntNzYwHRSn/Tm82DGzixTPt0TcTn3KYrk13XpRJuxMbbvHDM >> LfYG0zglGmVKUaWs4rBogh4H4OaiOIR8lORXSC8GRQjA1/C4c+FjIg+KeW5Yw2Ti >> XnG87BPyJ1TtPGWxxeKAk4tnkZwnZKtJOnHU/IfvTFOpECdBjojWnnc6VbQ1um0H >> WwjR6EcA4qxkkhND6ypIGkt9A4k3ZZvckCau52EgIn3pnwhk5OSw64MURJAEmn0= >> =vm/H >> -----END PGP SIGNATURE----- >> > > -- > 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
