** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1315580
Title:
FloatingIpNotAssociated results in BotoServerError: 500 Internal
Server Error
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Saw a tempest failure in the gate:
http://logs.openstack.org/32/91732/1/check/check-tempest-dsvm-
full/c0e77e9/console.html#_2014-05-02_07_29_01_528
2014-05-02 07:29:01.527 | Traceback (most recent call last):
2014-05-02 07:29:01.527 | File
"tempest/thirdparty/boto/test_ec2_instance_run.py", line 334, in
test_compute_with_volumes
2014-05-02 07:29:01.527 | address.disassociate()
2014-05-02 07:29:01.527 | File
"/usr/local/lib/python2.7/dist-packages/boto/ec2/address.py", line 126, in
disassociate
2014-05-02 07:29:01.527 | dry_run=dry_run
2014-05-02 07:29:01.527 | File
"/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py", line 1996, in
disassociate_address
2014-05-02 07:29:01.528 | return self.get_status('DisassociateAddress',
params, verb='POST')
2014-05-02 07:29:01.528 | File
"/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1182, in
get_status
2014-05-02 07:29:01.528 | response = self.make_request(action, params,
path, verb)
2014-05-02 07:29:01.528 | File
"/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1089, in
make_request
2014-05-02 07:29:01.528 | return self._mexe(http_request)
2014-05-02 07:29:01.528 | File
"/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1002, in _mexe
2014-05-02 07:29:01.528 | raise BotoServerError(response.status,
response.reason, body)
2014-05-02 07:29:01.528 | BotoServerError: BotoServerError: 500 Internal
Server Error
2014-05-02 07:29:01.528 | <?xml version="1.0"?>
2014-05-02 07:29:01.528 |
<Response><Errors><Error><Code>FloatingIpNotAssociated</Code><Message>Unknown
error
occurred.</Message></Error></Errors><RequestID>req-bd454aa5-541f-4e35-b050-b0a0a56afef4</RequestID></Response>
Seems to be during some pretty generic teardown during a test that was
otherwise passing...
The issue seems to be a race in the api, or a timeout on the test
side, there was two requests to disassociate the ip:
req-ce60e9aa-db14-4c93-b943-d3fcf51f9673 ->
http://logs.openstack.org/32/91732/1/check/check-tempest-dsvm-
full/c0e77e9/logs/screen-n-api.txt.gz#_2014-05-02_07_19_29_827
And then later another that raised the error:
req-bd454aa5-541f-4e35-b050-b0a0a56afef4 ->
http://logs.openstack.org/32/91732/1/check/check-tempest-dsvm-
full/c0e77e9/logs/screen-n-api.txt.gz#_2014-05-02_07_20_03_393
What confuses me is that later (after the failed request) - I see
another log line for req-ce60e9aa-db14-4c93-b943-d3fcf51f9673 that
seems to indicate success?
http://logs.openstack.org/32/91732/1/check/check-tempest-dsvm-
full/c0e77e9/logs/screen-n-api.txt.gz#_2014-05-02_07_20_04_099
So that doesn't seem right...
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1315580/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
