a6c231cdd7
When the OVS bridge is still being initialized we get a "failed to connect to socket" error when running ovs-ofctl. This shows up quite frequently in our functional tests and may be the source of their high failure rate. Ultimately we need to change the behavior of run_ofctl to not ignore errors by default, but this will require a lot of effort because there are many places that likely expect this behavior. As a workaround, this patch checks for the specific socket failure and attempts the command again up to 10 times, sleeping for 1 second between each attempt to wait for the bridge to be ready. Closes-Bug: #1550623 Closes-Bug: #1551593 Change-Id: I663a54608ed96133014104fe033ecea0a867ac4c |
||
---|---|---|
.. | ||
__init__.py | ||
test_config.py | ||
test_ovs_lib.py | ||
test_polling.py | ||
test_utils.py |