juju bootstrap in an existing environment destroys the environment

[James Troup]

Using juju-core 1.18.1-0ubuntu1 from Ubuntu 14.04, I bootstrapped a
juju environment in MAAS (1.5.2+bzr2282-0ubuntu0.2). This completed
successfully and I had a running environment.

I then hit up-arrow too many times by mistake and ran 'juju bootstrap'
again. It failed (as expected) but also destroyed my existing
environment (neither expected nor desired) with no warning or
interaction.

Obviously, this is a catastrophically bad failure mode.

Full log: https://pastebin.canonical.com/113355/

[James Troup (elmo)]

This bug has been fixed in later versions; I can no longer reproduce it with 1.20.1.

jujumanage@macon:~$ juju bootstrap
WARNING ignoring environments.yaml: using bootstrap config in file "/home/jujumanage/.juju/environments/maas.jenv"
ERROR environment is already bootstrapped
jujumanage@macon:~$ juju stat

However given the potential for data loss, I'd strongly suggest that we either SRU 1.20.1 or just the relevant patch to Ubuntu 14.04.

[Martin Packman (gz)]

I can't trivially reproduce this with either the 1.18 or trunk branches. It may be maas-provider or timing specific.

[Curtis Hovey (sinzui)]

This bug is a duplicate of Jame's first report. Since the conversation is here, I made the older bug the duplicate instead.

[Katherine Cox-Buday (cox-katherine-e)]

It appears that this may have been a result of errors not propagating correctly when examining an environment's configuration. Due to the nature of the bug, we had difficulty reproducing the exact issue, but feel this should probably address it. Please let us know if this is not the case.