armando-migliaccio 2051ffb822 Retry metadata request on connection refused error ... This testcase may fail intermittently on 'Connection refused' error. This could be due to the fact that the metadata proxy setup is not exactly complete at the time the request is issued; in fact there is no synchronization between the router being up and the metadata request being issued, and clearly this may be the reason of accidental but seldom failures. In order to rule out this possibility and stabilize the test, let's retry on connection refused only. If we continue to fail, then the next step would be to dump the content of iptables to figure out why the error occurs. Closes-bug: #1461172 Conflicts: neutron/tests/functional/agent/test_l3_agent.py Change-Id: I65a5bf4fbbcad6ba93a46d36cabe7844ff528d8d (cherry picked from commit 4b2e6842f3)		2015-10-12 13:58:31 +02:00
..
l3	Cleanup stale metadata processes on l3 agent sync	2015-07-30 12:49:59 +03:00
linux	Merge "func: Don't use private method of AsyncProcess" into stable/kilo	2015-10-07 23:50:00 +00:00
__init__.py	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
test_l3_agent.py	Retry metadata request on connection refused error	2015-10-12 13:58:31 +02:00
test_ovs_flows.py	Increase max attempts to 2 for pings on ARP tests	2015-07-13 12:39:03 +00:00
test_ovs_lib.py	Define bridge/port fixtures for OVS/LinuxBridge/Veth backends	2015-04-01 15:01:06 +00:00