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-7 netvirt <p>When using L3 DVR, creating a bridge br-ex that contains a port with no IP address and connecting to ODL results in ODL not pushing the normal and controller flow. The br-ex bridge will have no flows on it, while br-int will have flows.</p> <p>If you remove conf.db and restart ODL, then set ovs manager to be ODL, flows will show up if br-ex is created by ODL.</p> <p>Logs attached.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-7

L3 DVR pushes no flows when br-ex already exists

Bug Verified Done Bertrand Low Tim Rozet Tue, 22 Mar 2016 14:54:26 +0000 Mon, 30 Oct 2017 15:38:58 +0000 Mon, 29 Aug 2016 13:27:39 +0000 Beryllium General 0 4 <p>Attachment karaf.log has been added with description: Karaf log</p> <p>Attachment karaf.log has been added with description: CLI walkthrough</p> <p>(In reply to Timothy Rozet from comment #1)<br/> &gt; Created attachment 906 <span class="error">&#91;details&#93;</span><br/> &gt; CLI walkthrough</p> <p>Hi Timothy,</p> <p>The attachment 906 (CLI Walkthrough) looks to be the same as the attachment 905 (karaf.log). Could you also provide the local.conf files for the node setup. Any details to reproduce the problem would be greatly appreciated.</p> <p>Thanks, Vinh</p> <p>Hi Vinh,</p> <p> I think you can use this local.conf to stack up with L3 features so that br-ex is required.<br/> Steps top reproduce will be to</p> <p>a. stack up <br/> b. perform some operations<br/> c. unset Manager in OVS<br/> d. set MAnager as ODL:6640 to OVS<br/> e. The br-ex will be already there, so ODL may not install flows.</p> <p>Please try this.</p> <p>(In reply to Venkatrangan Govindarajan from comment #3)<br/> &gt; Hi Vinh,<br/> &gt; <br/> &gt; I think you can use this local.conf to stack up with L3 features so that<br/> &gt; br-ex is required.<br/> &gt; Steps top reproduce will be to<br/> &gt; <br/> &gt; a. stack up <br/> &gt; b. perform some operations<br/> &gt; c. unset Manager in OVS<br/> &gt; d. set MAnager as ODL:6640 to OVS<br/> &gt; e. The br-ex will be already there, so ODL may not install flows.<br/> &gt; <br/> &gt; Please try this.</p> <p>The problem still cannot reproduced with deleting and recreating the bridge after unset Manager. These are the CLI walk-through:</p> <p>$ sudo ovs-ofctl dump-flows br-ex -O OpenFlow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=19.211s, table=0, n_packets=0, n_bytes=0, dl_type=0x88cc actions=CONTROLLER:65535<br/> cookie=0x0, duration=19.211s, table=0, n_packets=0, n_bytes=0, priority=0 actions=NORMAL<br/> 1) $ sudo ovs-vsctl del-manager<br/> 2) $ sudo ovs-vsctl del-br br-ex <br/> 3) $ sudo ovs-vsctl add-br br-ex &#8211; set-controller br-ex tcp:10.128.0.3:6653<br/> 4) $ sudo ovs-ofctl dump-flows br-ex -O OpenFlow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> 5) $ sudo ovs-vsctl set-manager tcp:10.128.0.3:6640<br/> 6) $ sudo ovs-ofctl dump-flows br-ex -O OpenFlow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=5.898s, table=0, n_packets=0, n_bytes=0, dl_type=0x88cc actions=CONTROLLER:65535<br/> cookie=0x0, duration=5.898s, table=0, n_packets=0, n_bytes=0, priority=0 actions=NORMAL</p> <p>​However the problem can be reproduced (flows are not pushed) if I delete the flows instead of deleting and recreating the bridge in step 2) and 3).</p> <p>(In reply to Timothy Rozet from comment #1)<br/> &gt; Created attachment 906 <span class="error">&#91;details&#93;</span><br/> &gt; CLI walkthrough</p> <p>Hi Timothy,</p> <p>is it possible to send your CLI walkthrough for reproducing this bug?</p> <p>thanks.</p> <p>Hi Bertrand,<br/> We saw this in OPNFV Apex installer. The Installer creates br-ex and puts the a host port on it with no IP for DVR case, before it ever connects to ODL. It doesn't seem to happen every time. Give me a week or so to try to investigate and see if I can consistently reproduce.</p> <p>Thanks.</p> <p>gerrit - to be reviewed for the scenario Vinh described: <a href="https://git.opendaylight.org/gerrit/#/c/38895/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/38895/</a></p> <p>Just got back to this bug. I am seeing it still with Beryllium SR2:</p> <p><span class="error">&#91;root@overcloud-controller-0 log&#93;</span># ovs-ofctl -O openflow13 dump-flows br-int<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=8956.247s, table=0, n_packets=0, n_bytes=0, dl_type=0x88cc actions=CONTROLLER:65535<br/> cookie=0x0, duration=8956.247s, table=0, n_packets=0, n_bytes=0, priority=0 actions=goto_table:20<br/> cookie=0x0, duration=8956.247s, table=20, n_packets=0, n_bytes=0, priority=0 actions=goto_table:30<br/> cookie=0x0, duration=8956.247s, table=30, n_packets=0, n_bytes=0, priority=0 actions=goto_table:40<br/> cookie=0x0, duration=8956.247s, table=40, n_packets=0, n_bytes=0, priority=0 actions=goto_table:50<br/> cookie=0x0, duration=8956.247s, table=50, n_packets=0, n_bytes=0, priority=0 actions=goto_table:60<br/> cookie=0x0, duration=8956.247s, table=60, n_packets=0, n_bytes=0, priority=0 actions=goto_table:70<br/> cookie=0x0, duration=8956.247s, table=70, n_packets=0, n_bytes=0, priority=0 actions=goto_table:80<br/> cookie=0x0, duration=8956.247s, table=80, n_packets=0, n_bytes=0, priority=0 actions=goto_table:90<br/> cookie=0x0, duration=8956.247s, table=90, n_packets=0, n_bytes=0, priority=0 actions=goto_table:100<br/> cookie=0x0, duration=8956.247s, table=100, n_packets=0, n_bytes=0, priority=0 actions=goto_table:110<br/> cookie=0x0, duration=8956.247s, table=110, n_packets=0, n_bytes=0, priority=0 actions=drop<br/> <span class="error">&#91;root@overcloud-controller-0 log&#93;</span># ovs-ofctl -O openflow13 dump-flows br-ex<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> <span class="error">&#91;root@overcloud-controller-0 log&#93;</span># ovs-vsctl show<br/> a090eb87-75c0-4cef-80e5-c79cc81f9998<br/> Manager "tcp:192.0.2.8:6640"<br/> is_connected: true<br/> Bridge br-int<br/> Controller "tcp:192.0.2.8:6653"<br/> is_connected: true<br/> fail_mode: secure<br/> Port br-int<br/> Interface br-int<br/> type: internal<br/> Bridge br-ex<br/> Controller "tcp:192.0.2.8:6653"<br/> is_connected: true<br/> fail_mode: secure<br/> Port "ens8"<br/> Interface "ens8"<br/> Port br-ex<br/> Interface br-ex<br/> type: internal<br/> ovs_version: "2.5.0"</p> <p><span class="error">&#91;root@overcloud-controller-0 opendaylight&#93;</span># cat etc/custom.properties | grep ovsdb.l3<br/> ovsdb.l3.fwd.enabled=yes<br/> ovsdb.l3.arp.responder.disabled=no</p> <ol> <li>ovsdb.l3gateway.mac=00:00:5E:00:02:01</li> </ol> <p>Will attach all karaf logs</p> <p>Hi Timothy,</p> <p>my patch hasn't been merged yet so the SR2 distribution is expected to fail. You'd have to test with your own ODL build after applying my patch to see if the issue is resolved.</p> <p>thanks.</p> <p>Attachment br-ex_no_flows_karaf_logs.tar.gz has been added with description: Latest full karaf logs</p> <p>This behaviour is no longer present with patch <a href="https://git.opendaylight.org/gerrit/#/c/40744/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/40744/</a></p> <p>The br-ex flows are now showing up after switch is reconnected to ODL.</p> <p>Looks good in our OPNFV deploys. Thanks!</p> Development External issue ID 5582 External issue URL Rank 0|i01p53: