juju destroy-environment destroys other environments

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

On 2013-12-04 1:17, Aaron Bentley wrote:
> Public bug reported:
>
> I destroyed my "juju-ci" environment, and my "juju-ci-2"
> environment was also deleted. The environments had unique
> control-buckets.
>
> $ juju destroy-environment -e juju-ci WARNING: this command will
> destroy the "juju-ci" environment (type: openstack) This includes
> all machines, services, data and other resources.
>
> Continue [y/N]? y $ 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

I'm pretty sure we do a prefix match, and "juju-ci-machine-0" and
"juju-ci-2-machine-0" both match "juju-ci-". Probably we could force
the next bits and you'd only hit it if you did "juju-ci-machine" as
the other environment name.

I'm not 100% sure on that.

John
=:->

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

iEYEARECAAYFAlKfIUEACgkQJdeBCYSNAAO/RACgpAQIB0XOytaMr7FPm/ep16bP
YR8AoJHoiBTkXB0d/i4e32qQjBx6xiHr
=/ElA
-----END PGP SIGNATURE-----

Not actually critical (not a regression) as it has been the case since we implemented the openstack provider, but I'll see if we can at least do a bit better about our filtering.

I marked it critical because it is a way that users can accidentally destroy a production environment, which is what happened to me. It claims to be destroying one environment and then destroys another. Tremendously dangerous, and obviously no workaround exists, because once the environment is deleted, it's gone for good, including any unique data that may have been in that environment.

saucy has seen the end of its life and is no longer receiving any updates. Marking the saucy task for this ticket as "Won't Fix".