EC2 api call TerminateInstances returns the wrong response
Bug #862680 reported by
Clint Byrum
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Hengqing Hu | ||
pyjuju |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The EC2 api reference states that this should return a requestId and instancesSet which is a list of instance state changes.
TerminateInstances on nova-api returns a requestId and <return>
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: ec2 |
Changed in juju: | |
status: | New → Invalid |
Changed in nova: | |
assignee: | nobody → Hengqing Hu (hudayou) |
Changed in nova: | |
milestone: | none → essex-4 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
This causes juju to fail to wait for the entire environment to be shutdown because the initial terminate_instances does not return a list of shutting down instances.
$ juju -v destroy-environment environment' command finished successfully
2011-09-29 18:32:08,229 DEBUG Initializing juju destroy-environment runtime
WARNING: this command will destroy the 'canonistack' environment (type: ec2).
This includes all machines, services, data, and other resources. Continue [y/N]y
2011-09-29 18:32:10,608 INFO Destroying environment 'canonistack' (type: ec2)...
2011-09-29 18:32:12,802 INFO Waiting on 0 EC2 instances to transition to terminated state, this may take a while
2011-09-29 18:32:13,169 DEBUG Deleted environment security group 'juju-canonistack'
2011-09-29 18:32:13,170 INFO 'destroy_
With EC2 it would have waited for the 4 machines I had in the environment to terminate.