DisassociateAddress can cause Internal Server Error
Bug #1080406 reported by
Attila Fazekas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Michael Still | ||
Folsom |
Fix Released
|
Low
|
Vish Ishaya | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have an allocated, but not associated address and I call the address.
query string: AWSAccessKeyId=
=2012-06-01
For the response I got:
HTTP Status: 500
EC2 Error_Code: "500" (Not a valid EC2 error code)
The api.log log attached.
I am using the stable/folsom.
Related branches
lp://staging/~gandelman-a/ubuntu/quantal/nova/2012.2.1
- Openstack Ubuntu Testers: Pending requested
-
Diff: 121 lines (+100/-4)1 file modifieddebian/changelog (+100/-4)
CVE References
tags: | added: ec2 |
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: folsom-backport-potential |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
Changed in nova (Ubuntu Quantal): | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
tags: | removed: folsom-backport-potential |
tags: | added: tempest |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
Interestingly, euca2ools retries forever (well, as long as I could be bothered to wait) in this scenario.