Public bug reported:
Got a failured temptest test in the gate:
2014-06-23 20:41:24.763 |
tempest.api.compute.servers.test_server_rescue.ServerRescueTestXML.test_rescued_vm_associate_dissociate_floating_ip[gate]
2014-06-23 20:41:24.763 |
-------------------------------------------------------------------------------------------------------------------------
2014-06-23 20:41:24.763 |
2014-06-23 20:41:24.763 | Captured traceback:
2014-06-23 20:41:24.763 | ~~~~~~~~~~~~~~~~~~~
2014-06-23 20:41:24.763 | Traceback (most recent call last):
2014-06-23 20:41:24.763 | File
"tempest/api/compute/servers/test_server_rescue.py", line 109, in
test_rescued_vm_associate_dissociate_floating_ip
2014-06-23 20:41:24.764 | self.server_id)
2014-06-23 20:41:24.764 | File
"tempest/services/compute/xml/floating_ips_client.py", line 100, in
disassociate_floating_ip_from_server
2014-06-23 20:41:24.764 | resp, body = self.post(url, str(doc))
2014-06-23 20:41:24.764 | File "tempest/common/rest_client.py", line
218, in post
2014-06-23 20:41:24.764 | return self.request('POST', url,
extra_headers, headers, body)
2014-06-23 20:41:24.764 | File "tempest/common/rest_client.py", line
430, in request
2014-06-23 20:41:24.764 | resp, resp_body)
2014-06-23 20:41:24.764 | File "tempest/common/rest_client.py", line
497, in _error_checker
2014-06-23 20:41:24.764 | raise
exceptions.UnprocessableEntity(resp_body)
2014-06-23 20:41:24.764 | UnprocessableEntity: Unprocessable entity
2014-06-23 20:41:24.764 | Details: {'message': 'Floating ip 172.24.4.1
is not associated with instance aa77a874-e802-43f0-beb5-e9c91d86519b.', 'code':
'422'}
I'm trying to do log stash more, cause it seems like that helps
something? It does sorta look like this one happens more today than the
previous run of the mill failures:
http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkZsb2F0aW5nIGlwIDE3Mi4yNC40LjEgaXMgbm90IGFzc29jaWF0ZWQgd2l0aCBpbnN0YW5jZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDAzNTU4OTA3MTI2fQ==
but, idk, I never feel like the reporting the symptom is really the bug?
I see errors in the n-cpu logs that look more like something broke:
http://logs.openstack.org/91/101991/1/check/check-tempest-dsvm-
full/ddf95f6/logs/screen-n-cpu.txt.gz?#_2014-06-23_20_39_05_833
oh well, I don't know why for some reason still think filing these bugs
is useful to someone... let me know.
** Affects: nova
Importance: Undecided
Status: New
--
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/1333434
Title:
Floating ip 172.24.4.1 is not associated with instance
Status in OpenStack Compute (Nova):
New
Bug description:
Got a failured temptest test in the gate:
2014-06-23 20:41:24.763 |
tempest.api.compute.servers.test_server_rescue.ServerRescueTestXML.test_rescued_vm_associate_dissociate_floating_ip[gate]
2014-06-23 20:41:24.763 |
-------------------------------------------------------------------------------------------------------------------------
2014-06-23 20:41:24.763 |
2014-06-23 20:41:24.763 | Captured traceback:
2014-06-23 20:41:24.763 | ~~~~~~~~~~~~~~~~~~~
2014-06-23 20:41:24.763 | Traceback (most recent call last):
2014-06-23 20:41:24.763 | File
"tempest/api/compute/servers/test_server_rescue.py", line 109, in
test_rescued_vm_associate_dissociate_floating_ip
2014-06-23 20:41:24.764 | self.server_id)
2014-06-23 20:41:24.764 | File
"tempest/services/compute/xml/floating_ips_client.py", line 100, in
disassociate_floating_ip_from_server
2014-06-23 20:41:24.764 | resp, body = self.post(url, str(doc))
2014-06-23 20:41:24.764 | File "tempest/common/rest_client.py",
line 218, in post
2014-06-23 20:41:24.764 | return self.request('POST', url,
extra_headers, headers, body)
2014-06-23 20:41:24.764 | File "tempest/common/rest_client.py",
line 430, in request
2014-06-23 20:41:24.764 | resp, resp_body)
2014-06-23 20:41:24.764 | File "tempest/common/rest_client.py",
line 497, in _error_checker
2014-06-23 20:41:24.764 | raise
exceptions.UnprocessableEntity(resp_body)
2014-06-23 20:41:24.764 | UnprocessableEntity: Unprocessable entity
2014-06-23 20:41:24.764 | Details: {'message': 'Floating ip
172.24.4.1 is not associated with instance
aa77a874-e802-43f0-beb5-e9c91d86519b.', 'code': '422'}
I'm trying to do log stash more, cause it seems like that helps
something? It does sorta look like this one happens more today than
the previous run of the mill failures:
http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkZsb2F0aW5nIGlwIDE3Mi4yNC40LjEgaXMgbm90IGFzc29jaWF0ZWQgd2l0aCBpbnN0YW5jZVwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDAzNTU4OTA3MTI2fQ==
but, idk, I never feel like the reporting the symptom is really the
bug? I see errors in the n-cpu logs that look more like something
broke:
http://logs.openstack.org/91/101991/1/check/check-tempest-dsvm-
full/ddf95f6/logs/screen-n-cpu.txt.gz?#_2014-06-23_20_39_05_833
oh well, I don't know why for some reason still think filing these
bugs is useful to someone... let me know.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1333434/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
