https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-348 netvirt <p>Using Boron-SR2 artifact, OpenStack mitaka.<br/> The networking setup is like this:</p> <p>external-interface &lt;<del>&gt; ext-linux-bridge &lt;-A</del>&gt; br-floating(ovs bridge) &lt;-&gt; br-int</p> <p>When ovs is restarted, port A ends up misconfigured.<br/> I've collected the logs from such a restart (due to a segfault on the ovs side-working on that). The way this happens makes me think that netvirt pushes some configuration that it should. </p> <p>To reproduce:</p> <p>service openvswitch-switch restart</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-348

ODL breaks ovs switch config on reconnect

Bug Resolved Cannot Reproduce Unassigned Romanos Skiadas Mon, 12 Dec 2016 09:57:06 +0000 Thu, 19 Oct 2017 21:28:00 +0000 Mon, 12 Dec 2016 16:14:11 +0000 Boron General 0 1 <p>&gt;netvirt pushes some configuration that it should<br/> should not*</p> <p>Attachment ovs-vswitchd.log has been added with description: ovs log</p> <p>Attachment ovs-vsctl has been added with description: ovs vsctl</p> <p>Attachment br-ex has been added with description: ifcfg of linux bridge</p> <p>Attachment port-ifcfg has been added with description: ifcfg of br-ex to br-floating port</p> <p>Attachment karafaa has been added with description: karaf log 1</p> <p>Attachment karafab has been added with description: karaf log 2</p> <p>Attachment karafac has been added with description: karaf log 3/4</p> <p>Attachment karafad has been added with description: karaf log 4/4</p> <p>Hi Skiadas,</p> <p>I'm closing this on invalid, unless you have a specific reason for thinking this is ODL related..<br/> Currently the only thing ODL does for your 'br-floating' bridge is add a patch port in it. Nothing else.</p> <p>The only bridge that is fully controlled by ODL is the br-int bridge, any other bridge is assumed to pre-exist and not modified on purpose (except addition of patch port).</p> <p>This seems like an OVS bug to me, I have previously seen similar issues when OVS restarts and particularily when it crashes. It's not cleaning up the previous socket so you reach this error:</p> <p>2016-12-07T10:23:16.672Z|00042|netdev|WARN|trying to create netdev p_ff798dba-0 of different type internal, already is system<br/> 2016-12-07T10:23:16.672Z|00043|bridge|WARN|could not open network device p_ff798dba-0 (File exists)</p> <p>As a workaround you can try deleting the socket for this port and restart ovs, it should fix things.</p> Development External issue ID 7342 External issue URL Rank 0|i01r8v: