ec2: destroy-controller blows the rate limit trying to delete security group - can leave instances around
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
Bug Description
Repro:
1. Deploy largish environment, I had the one from LP #1511659
2. In repo'ing 1511659, stop a machine that has been deployed by sshing to the machine and sudo shutdown
2a. check in AWS console that that the machine is in STOPPED state (not TERMINATED)
3. juju kill-controller ap-southeast-2
WARNING! This command will destroy the "ap-southeast-2" controller.
This includes all machines, services, data and other resources.
Continue [y/N]? y
Destroying controller "ap-southeast-2"
Waiting for resources to be reclaimed
All hosted environments reclaimed, cleaning up controller machines
WARNING could not delete security group "juju-349b8bc2-
WARNING could not delete security group "juju-349b8bc2-
(repeated)
WARNING could not delete security group "juju-349b8bc2-
Helpful suggestion from a duplicate bug:
This warning isn't helpful and the user can't act upon it. It's working according to plan and the output should be more clear. I'd suggest:
% juju destroy-controller b3aws
WARNING! This command will destroy the "local.b3aws" controller.
This includes all machines, services, data and other resources.
Continue [y/N]? y
Destroying controller "local.b3aws"
Cleaning up services and machines.......(and to do a . for each of these warnings as an attempt at a progress-like meter)
| summary: |
- environs/ec2: a stopped machine will cause kill-machine to fail and blow - the rate limit + environs/ec2: a stopped machine will cause kill-controller to fail and + blow the rate limit |
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| milestone: | none → 2.0-beta1 |
| Cheryl Jennings (cherylj) wrote Re: environs/ec2: a stopped machine will cause kill-controller to fail and blow the rate limit | #1 |
| Changed in juju-core: | |
| milestone: | 2.0-beta1 → 2.0-beta2 |
| Changed in juju-core: | |
| milestone: | 2.0-beta2 → 2.0-beta3 |
| summary: |
- environs/ec2: a stopped machine will cause kill-controller to fail and - blow the rate limit + environs/ec2: kill-controller / destroy-controller blow the rate limit + trying to delete security group |
| Cheryl Jennings (cherylj) wrote Re: environs/ec2: kill-controller / destroy-controller blow the rate limit trying to delete security group | #2 |
| Changed in juju-core: | |
| milestone: | 2.0-beta3 → 2.0-beta4 |
| tags: | added: 2.0-count |
| description: | updated |
| summary: |
- environs/ec2: kill-controller / destroy-controller blow the rate limit - trying to delete security group + ec2: destroy-controller blow the rate limit trying to delete security + group - can leave instances around |
| Cheryl Jennings (cherylj) wrote Re: ec2: destroy-controller blow the rate limit trying to delete security group - can leave instances around | #3 |
| tags: | added: ci jujuqa |
| summary: |
- ec2: destroy-controller blow the rate limit trying to delete security + ec2: destroy-controller blows the rate limit trying to delete security group - can leave instances around |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Anastasia (anastasia-macmood) |
| Anastasia (anastasia-macmood) wrote | #4 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta4 → none |
| milestone: | none → 2.0-beta4 |
As per bug #1542992, this doesn't require a stopped machine to hit this issue.