Failed bootstrap does not clean up failed environment w/o --force and error message is unhelpful

[Alexis Bruemmer]

When a bootstrap fails juju thinks the environment exists even though the bootstrapped failed. When bootstrap fails juju should clean up the environment.

[Curtis Hovey (sinzui)]

This is probably a duplicate of bug 1257758 or bug 1212177. In general, Juju is leaving jenv files on the local disk or something in provider storage/bucket/container.

[Martin Packman (gz)]

A paste of where the bootstrap failed and what the next bootstrap attempted claimed was the problem would help classify this bug.

[Alexis Bruemmer (alexis-bruemmer)]

Further investigation this was really two problems, I will break the problem into two bugs. For the first bug here are the recreate steps:

1) juju switch local
2) juju bootstrap
3) wait until "Bootstrapping Juju machine agent" kill the bootstrap with ctrl-c

The bootstrap fails:

ERROR failed to bootstrap environment: exit status 1

4) attempt to bootstrap again:
~/gowork$ juju bootstrap
WARNING ignoring environments.yaml: using bootstrap config in file "/home/alexisb/.juju/environments/local.jenv"
WARNING This juju environment is already bootstrapped. If you want to start a new Juju
environment, first run juju destroy-environment to clean up, or switch to an
alternative environment.
ERROR environment is already bootstrapped

5) run "juju destroy-environment local" as suggested; after nearly a 5 minute delay get:
ERROR cannot connect to API: unable to connect to "wss://10.0.3.1:17070/environment/8e86ec81-2f62-42f2-8247-a82a4881724f/api"

This is an unhelpful error given what the user needs to run juju destroy-environment with the --force option.

[Alexis Bruemmer (alexis-bruemmer)]

Proposed Fix: https://github.com/juju/juju/pull/3630

[Anastasia (anastasia-macmood)]

Marking as
'Invalid' for Juju 2.0 since this area changed dramatically (for e.g. no more .jenv files)
and
'Won't Fix' for 1.25 is it is in support mode and we accept 'Critical' bugs only.