yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47218
[Bug 1551593] Re: functional test failures caused by failure to setup OVS bridge
*** This bug is a duplicate of bug 1547486 ***
https://bugs.launchpad.net/bugs/1547486
Reviewed: https://review.openstack.org/286428
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a6c231cdd731dae900c372799a890407bbc24a2c
Submitter: Jenkins
Branch: master
commit a6c231cdd731dae900c372799a890407bbc24a2c
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date: Mon Feb 29 21:28:48 2016 -0800
Make run_ofctl check for socket error
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
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1551593
Title:
functional test failures caused by failure to setup OVS bridge
Status in neutron:
Fix Released
Bug description:
Right now we get random functional test failures and it seems to be
related to the fact that we only log and error and continue when a
flow fails to be inserted into a bridge:
http://logs.openstack.org/90/283790/10/check/gate-neutron-dsvm-
functional/ab54e0a/logs/neutron.tests.functional.agent.test_ovs_flows.ARPSpoofOFCtlTestCase.test_arp_spoof_doesnt_block_ipv6_native_.log.txt.gz#_2016-03-01_01_47_17_903
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1551593/+subscriptions
References