juju-quickstart destroys existing AWS environment

[Artur Tyloch]

It seems in juju-quickstart 1.4.4 exisitng environment is destroyed without warning and new ne created when you have outdated or missing enviroment.jenv file (missing e.g. because another user is using the same AWS credencials).

How to replicate issue:
1. Create new AWS juju environment (env name e.g. testaws ) using :
juju switch testaws
juju-quickstart

2. Delete local testaws.jenv

3. run again for testaws:
juju-quickstart

Old environment will be destroyed and new bootstraped without warning.
AFAIR in previous version of juju-quickstart in a such case there was an error i.e new environment was not created.

[Jay R. Wren (evarlast)]

Looks like it is this juju bug:
https://bugs.launchpad.net/juju-core/+bug/1336843

[Francesco Banconi (frankban)]

This is related to juju-core and to the bug Jay linked above.
The quickstart approach here is the only one possible: we always try to bootstrap the environment, and if an "already bootstrapped" error is returned by juju we try to reuse the environment.
1.21-alpha2 includes a fix, but its behavior is still suboptimal for quickstart needs: added a comment in bug 1336843

[Richard Harding (rharding)]

Marking this as a dupe of the juju-core bug. It's fixed in the next release. If you hit this while testing the alpha please let us know and we'll look into it further.