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-276 netvirt <p>When using an external bridge "br-ex" patched to br-int, br-int is missing the table0 flow to match traffic sent from br-ex patch port. See attached karaf logs and ovs output. There was one error message in OVS log:<br/> 2016-11-15T11:11:58.601Z|00039|connmgr|INFO|br-int&lt;-&gt;tcp:192.0.2.10:6653: sending OFPBAC_BAD_OUT_GROUP error reply to OFPT_FLOW_MOD message</p> <p>Operating System: Linux<br/> Platform: All</p> NETVIRT-276

External DVR flow missing when using external OVS bridge

Bug Resolved Done Unassigned Tim Rozet Tue, 15 Nov 2016 17:35:22 +0000 Thu, 19 Oct 2017 21:28:03 +0000 Fri, 18 Nov 2016 21:35:34 +0000 Boron General 0 3 <p>Attachment karaf_no_external_flow.zip has been added with description: Karaf logs</p> <p>Attachment ovs_output.txt has been added with description: ovs outputs</p> <p>We are using this feature quite a lot in our lab.</p> <p>Could you please add the following debug information:</p> <ul> <li>neutron net-show &lt;external-network&gt;</li> <li>DS outputs: config/ietf-interfaces:interfaces, operational/ietf-interfaces:interfaces-state, config:elan:elan-instances</li> </ul> <p>I found that the external network was being created without passing provider type "flat" or the physical network (in our case "datacentre"). This causes the external network to be created as a vxlan provider network. In L3 agent this has worked in the past because the agent just uses 'br-ex' by default, and this also used to work with old netvirt.</p> <p>Once I re-created external network with --provider:network_type flat --provider:physical_network datacentre I see the flows. However, floating IP would still not work. After a fresh install with today's autorelease, I am able to create an external network and ssh into the instance over floating IP. However, I am unable to ping the router external IP. Also, after deleting and recreating the external network (and reassigning a new floating IP), floating IPs break and I cannot ssh into the instance anymore from external net. </p> <p>I think these 2 issues are 2 different bugs from this one. But for this bug, I think we want to throw an error when an external network is created for type vxlan, right?</p> <p>Happy to hear you were able to find the problem, this was one of the options I wanted to rule out using "neutron net-show". I wonder whether this configuration should've been blocked by openstack or not.</p> <p>In any case, both other bugs you were mentioning are already opened:</p> <ul> <li><a href="https://bugs.opendaylight.org/show_bug.cgi?id=7119" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=7119</a> - We figured out this bug is due to a public net delete/create as you mentioned. Currently there is a fix undergoing review.</li> </ul> <ul> <li><a href="https://trello.com/c/aeVj3Qss" class="external-link" target="_blank" rel="nofollow noopener">https://trello.com/c/aeVj3Qss</a> - Task to implement router gateway interface ping responder in Carbon. Currently the new netvirt only implements a ping responder for router interfaces (internal interfaces of a router).</li> </ul> <p>Do you think we can close this bug?</p> <p>Sorry, I missed your question regarding throwing an error for this. Let's keep this bug as a reminder, but we should probably lower its severity</p> <p>After talking with Assaf from Neutron team, VXLAN should not be an allowed external network type. I will take it up with the Neutron project and we can close this bug.</p> <p>Makes sense, thanks!</p> Development External issue ID 7191 External issue URL Rank 0|i01qsv: