500 on deleteing a not existing ec2 security group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Liyingjun |
Bug Description
Looks like there are 2 reason for seeing 500 errors on not existing ec2 security group delete attempt:
* Unexpected TypeError raised: expected string or buffer
* Unexpected UnboundLocalError raised: local variable 'group' referenced before assignment
Since it is server error the euca2ools automatically and silently retries the request multiple (unlimited?) times.
1. source the ec2 credentials:
$source /opt/stack/
2.a:
$ euca-delete-group --debug 42
...
2015-01-13 09:57:02,907 euca2ools [DEBUG]:Received 500 response. Retrying in 1.9 seconds
2.b:
$ euca-delete-group --debug fortytwo
Relevant lines from the n-api log (It does not contains a full trace, however on this kind of errors it should):
action: DeleteSecurityGroup __call__ /opt/stack/
arg: GroupName val: fortytwo __call__ /opt/stack/
Neutron security group fortytwo not found get /opt/stack/
Unexpected UnboundLocalError raised: local variable 'group' referenced before assignment
EC2 error response: UnboundLocalError: Unknown error occurred. ec2_error_response /opt/stack/
Note: The issue seen in a neutron setup.
tags: | added: ec2 |
tags: | added: network |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in nova: | |
assignee: | nobody → Liyingjun (liyingjun) |
Changed in nova: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-3 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/148459
Review: https:/