destroy-enviroment --force destroy all aws instances
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
Medium
|
Unassigned | ||
Bug Description
While ago i set environment in AWS account whit some ec2 instances. Just for testing propose i run "juju destroy-enviroment --force" and it terminate all my AWS instances, including instances not created by juju.
Maybe there need to be a warning about this? or double check if it's really happening.
| lithium (rudicba) wrote : | #2 |
This was long ago, already delete that environment because i was just testing/learning. I think it was using juju 1.20 from Ubuntu official repository.
Sorry for not report at time, at end of next week i could try in a new aws account .
| tags: | added: destroy-environment ec2-provider |
| Launchpad Janitor (janitor) wrote : | #3 |
[Expired for juju-core because there has been no activity for 60 days.]
| Changed in juju-core: | |
| status: | Incomplete → Expired |
| Tim Penhey (thumper) wrote : | #4 |
We should double check this with the current juju.
| Changed in juju-core: | |
| status: | Expired → Triaged |
| importance: | Undecided → High |
| Cheryl Jennings (cherylj) wrote : | #5 |
Tried to recreate this with 1.25 an a simple EC2 environment and the machines that were not created by Juju were not destroyed with --force.
| Changed in juju-core: | |
| status: | Triaged → Incomplete |
| importance: | High → Medium |
| Launchpad Janitor (janitor) wrote : | #6 |
[Expired for juju-core because there has been no activity for 60 days.]
| Changed in juju-core: | |
| status: | Incomplete → Expired |
What version of Juju were you using? Can you share your environment.yaml entry (confidential bits removed)?