false "environment is already bootstrapped" message

[Aaron Bentley]

Today I tried to bootstrap the environment that was torn down in bug #1257481. But juju falsely claims it has already been bootstrapped. Even removing the .jenv file doesn't fix it.

$ juju bootstrap
ERROR environment is already bootstrapped
$ juju status
ERROR Unable to connect to environment "juju-ci-2".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
no instances found

$ jnova list
$ rm ~/.juju/environments/juju-ci-2.jenv
$ juju bootstrap
ERROR environment is already bootstrapped

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-12-04 18:29, Aaron Bentley wrote:
> Public bug reported:
>
> Today I tried to bootstrap the environment that was torn down in
> bug #1257481. But juju falsely claims it has already been
> bootstrapped. Even removing the .jenv file doesn't fix it.
>
> $ juju bootstrap ERROR environment is already bootstrapped $ juju
> status ERROR Unable to connect to environment "juju-ci-2". Please
> check your credentials or use 'juju bootstrap' to create a new
> environment.
>
> Error details: no instances found
>
> $ jnova list $ rm ~/.juju/environments/juju-ci-2.jenv $ juju
> bootstrap ERROR environment is already bootstrapped
>
> ** Affects: juju-core Importance: High Status: Triaged
>

The actual item is that there is a "provider-state" file in the
provider storage (which is what we use to track what instance should
be machine-0).
Running 'juju destroy-environment juju-ci-2' cleans out that
information and gets you cleaned up.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKfZiIACgkQJdeBCYSNAANIBwCdGe9yocvrGo/DRmG+PBLZXpD1
QwAAmwQiJCuKdPJvh7v0x1hgKmsOhbtS
=1atD
-----END PGP SIGNATURE-----

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-12-04 18:29, Aaron Bentley wrote:
> Public bug reported:
>
> Today I tried to bootstrap the environment that was torn down in
> bug #1257481. But juju falsely claims it has already been
> bootstrapped. Even removing the .jenv file doesn't fix it.
>
> $ juju bootstrap ERROR environment is already bootstrapped $ juju
> status ERROR Unable to connect to environment "juju-ci-2". Please
> check your credentials or use 'juju bootstrap' to create a new
> environment.
>
> Error details: no instances found
>
> $ jnova list $ rm ~/.juju/environments/juju-ci-2.jenv $ juju
> bootstrap ERROR environment is already bootstrapped
>
> ** Affects: juju-core Importance: High Status: Triaged
>

There is likely to be a 'provider-state' file still stored in the
control bucket listed for your 'juju-ci-2' environment. You can either
delete that file using swift tools, or use 'juju destroy-environment'.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKkT0sACgkQJdeBCYSNAAP0qACg2YAQXXypAslWfHI3n0J/+e3A
I/UAoLl1IVsuIO96iWi70uXfoagxnhIA
=ZGj6
-----END PGP SIGNATURE-----

[Dimiter Naydenov (dimitern)]

The environment wasn't destroyed properly, due to the previous bug mentioned, it was trashed. Running destroy-environment juju-ci-2 actually fixed the problem, so I'm marking this as Invalid, as agreed in a team discussion.

[Aaron Bentley (abentley)]

I have discussed it with Curtis, and we agree that it is a bug. Yes, destroy-environment may fix the situation, but that is a workaround. Having a workaround does not make a bug invalid.

The bug is that "bootstrap" claims it's already bootstrapped and "status" claims that it is not bootstrapped. They cannot both be right. There should be a single definition of "bootstrapped" that is used by both commands, so that they do not contradict each other.