Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Here is the latest marked fail - 
> http://logs.openstack.org/28/79628/4/check/check-tempest-dsvm-neutron/11f8293/

So,
> 
looking at this a little bit, you can see from the n-cpu log that
it is getting failures when talking to neutron. Specifically, from
neutronclient:

throwing ConnectionFailed : timed out _cs_request
ConnectionFailed: Connection to neutron failed: Maximum attempts reached

- From a brief look at neutronclient, it looks like it tries several
times to send a request, before it falls back to the above error.
Given the debug "timed out" log there, I would assume that neutron's
API isn't accepting the connection in time.

Later in the log, it successfully reaches neutron again, and then
falls over again in the same way. This is a parallel job, so load is
high, which makes me suspect just a load issue.

- From talking to salv-orlando on IRC just now, it sounds like this
might just be some lock contention on the Neutron side, which is
slowing it down enough to cause failures occasionally.

- --Dan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTIbxoAAoJEBeZxaMESjNVB4IH/0wzaRhW/xkuUbFxNsSbRRt5
8EJdBkDJHfFQW6VQM6GqmvyZOVFkTLOhdMGF1dgWLBTTkGhmOVRiwdkim059sPd4
3EwUH3ZhSQg8n/rSAoS0rb1nFKaCt6D76DNJR5LXBCd89k6d/0q8SAkOgwNg7H82
oS17CjnLYvUfvF0JqSmKNt4ter1zMSXMZXNe8z09mKqZBTC4vNWIskv2yLgUbecv
Sb6NVc+HFkCk3t5MlKlM8fnLIoF2b4F0w0rCSJPV9txXWL2ijiaFIncyTYSFSuOp
NE1kdEAuZOIUnnZW3udEyb4QQS3HhRbVvRHJbnTAOVLGw5ijp+1V5FoipizA3v0=
=lVal
-----END PGP SIGNATURE-----