Activity log for bug #1257481

Date Who What changed Old value New value Message
2013-12-03 21:17:54 Aaron Bentley bug added bug
2013-12-04 12:39:34 John A Meinel juju-core: importance Critical High
2013-12-04 12:39:34 John A Meinel juju-core: status Triaged In Progress
2013-12-04 12:39:34 John A Meinel juju-core: assignee John A Meinel (jameinel)
2013-12-04 15:12:25 Launchpad Janitor branch linked lp:~jameinel/juju-core/openstack-filter-1257481
2013-12-08 09:45:52 John A Meinel nominated for series juju-core/1.16
2013-12-08 09:45:52 John A Meinel bug task added juju-core/1.16
2013-12-08 09:46:07 John A Meinel juju-core/1.16: importance Undecided High
2013-12-08 09:46:07 John A Meinel juju-core/1.16: status New In Progress
2013-12-08 09:46:07 John A Meinel juju-core/1.16: assignee John A Meinel (jameinel)
2013-12-08 09:46:12 John A Meinel juju-core/1.16: milestone 1.16.5
2013-12-08 09:46:14 John A Meinel juju-core: milestone 1.17.0
2013-12-09 10:52:15 Go Bot juju-core/1.16: status In Progress Fix Committed
2013-12-10 06:25:38 Go Bot juju-core: status In Progress Fix Committed
2013-12-10 19:58:51 Curtis Hovey juju-core/1.16: status Fix Committed Fix Released
2013-12-20 17:44:13 Curtis Hovey juju-core: status Fix Committed Fix Released
2014-02-07 12:28:21 James Page bug task added juju-core (Ubuntu)
2014-02-07 12:28:50 James Page nominated for series Ubuntu Saucy
2014-02-07 12:28:50 James Page bug task added juju-core (Ubuntu Saucy)
2014-02-07 12:29:33 James Page juju-core (Ubuntu): status New Fix Released
2014-02-07 14:03:26 Launchpad Janitor branch linked lp:~james-page/ubuntu/saucy/juju-core/1.16.5
2014-04-10 10:36:36 James Page description 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 [Impact] Users inadvertently destroy all environments that they own, not just the target one. [Test Case] juju bootstrap env1 juju bootstrap env2 juju destroy-environement env1 # both environments destroyed [Regression Potential Minimal, the fix tightens up the pattern match used to determine which machines to destroy. [Original Bug Report] 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
2014-12-05 07:03:03 Rolf Leggewie juju-core (Ubuntu Saucy): status New Won't Fix