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.
Reviewed: https:/ /review. openstack. org/233544 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=2051ffb822d d89112cf4168165 9a2d434bb8534d
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit 2051ffb822dd891 12cf41681659a2d 434bb8534d
Author: armando-migliaccio <email address hidden>
Date: Mon Sep 7 04:53:50 2015 -0700
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: tests/functiona l/agent/ test_l3_ agent.py
neutron/
Change-Id: I65a5bf4fbbcad6 ba93a46d36cabe7 844ff528d8d cd963f560bc0684 9b4b7bb1eb)
(cherry picked from commit 4b2e6842f320405