Reviewed: https://review.openstack.org/441447 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6975e2a48e85a5f0f198e2af3e99bc06dd409eaa Submitter: Jenkins Branch: master
commit 6975e2a48e85a5f0f198e2af3e99bc06dd409eaa Author: Terry Wilson <[email protected]> Date: Fri Mar 3 14:00:39 2017 -0600 Ensure ovsdb_connection enabled before calling monitor ovsdb-client monitor attempts to connect to ovs via the ovsdb_connection if it is set. Since it is set by default, we need to ensure that OVS is listening on the socket before calling ovsdb-client monitor. Closes-Bug: #1669893 Depends-On: Ibde5417d005265d27e939ca29788c21f73b38980 Change-Id: Ia34b9d599b522dd12ef088100c2b68a75a78d797 ** 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/1669893 Title: ovsdb-monitor fails to connect to tcp port when vsctl driver is used Status in neutron: Fix Released Bug description: It can be spotted in some functional test runs where vsctl flavours of tests are triggered before any native flavored test enables the manager port for tcp. For example, http://logs.openstack.org/18/441218/1/check/gate-neutron-dsvm- functional-ubuntu-xenial/08292fe/logs/dsvm-functional- logs/neutron.tests.functional.agent.l2.extensions.test_ovs_agent_qos_extension.TestOVSAgentQosExtension.test_policy_rule_delete_vsctl_.txt.gz#_2017-03-03_16_53_30_358 This is because of https://review.openstack.org/#/c/407813/ that assumed that we use native. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1669893/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
