Public bug reported:
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.
** Affects: juju-quickstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1385407
Title:
juju-quickstart destroys existing AWS environment
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1385407/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
