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/OVSDB-200 ovsdb <p>Build#: Lithium-SR1 Build<br/> Openstack: stable/kilo</p> <p>local.conf snip<br/> =======<br/> enable_plugin networking-odl <a href="https://github.com/stackforge/networking-odl" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/stackforge/networking-odl</a> stable/kilo<br/> Q_PLUGIN=ml2<br/> ENABLE_TENANT_TUNNELS=True<br/> Q_ML2_TENANT_NETWORK_TYPE=vxlan<br/> PUBLIC_INTERFACE=em3<br/> ODL_LOCAL_IP=20.1.1.3<br/> disable_service q-l3<br/> Q_L3_ENABLED=True<br/> ODL_L3=True</p> <p>ODL custom.properites<br/> ================<br/> ovsdb.l3.fwd.enabled=yes<br/> ovsdb.l3gateway.mac=00:00:5E:00:02:01 (tested with both enable/disabled option)</p> <p>Environment<br/> ============<br/> Openstack controller &amp; 10 compute node connected with ODL as external mode.</p> <p>Problem:<br/> ==========<br/> 1.Have create the VxLAN tunnel Network (3.3.3.0/24) and spawed 1 VM instance on each compute node (i.e 12 compute node).Respective OF entries created on br-int (as per sudo ovs-ofctl -O OpenFlow13 dump-flows br-int)</p> <p>2.Unstacked the all 12 compute node </p> <p>3.Check br-int OF entries on openstack controller side. <br/> (sudo ovs-ofctl -O OpenFlow13 dump-flows br-int)</p> <p> Expected all OF entries needs to be removed either by OF flow expire mechanism or unstack event from compute node side.</p> <p> Current behaviour all 12 VM Instance OF entries retained untill openstack controller unstacked and restacked.</p> <p>sudo ovs-ofctl -O OpenFlow13 dump-flows br-int</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-200

Stale OF entries retained in br-int flow table on openstack-controller side,when VM resides on unstacked compute node

Bug Resolved Cannot Reproduce Unassigned Vasanthan Balasubramaniyan Tue, 1 Sep 2015 12:43:12 +0000 Thu, 19 Oct 2017 21:29:11 +0000 Wed, 30 Sep 2015 10:53:37 +0000 unspecified openstack.net-virt 0 2 <p>The OVS cleanup is not initiated by the ODL controller. It is initiated by unstack.sh script. </p> <p>The script file /opt/stack/networking-odl/devstack/plugin.sh has a function stop_opendaylight-compute(). This function will try to delete all the ports and bridges of the OVS. This issue is not related to ODL and it should be related to openstack.</p> <p>Attachment Controller_Node_br_int.txt has been added with description: OpenstackCOntroller_BR_INT_OFENTRIES</p> <p>Compute node br-int OF entries and you can see stale OF entries on controller_br_int attachment</p> <p>Attachment compute_node_br_int.txt has been added with description: openstackComputeNode_BRINT_OFEntries</p> <p>Flow programming(i.e flow creation) done thru ODL controller,so respective flow deletion also needs to be performed thru ODL Controller.</p> <p>Step to recreate :<br/> ==================<br/> 1.Stack the Openstack controller and one compute node (i.e used one compute node because to isolated stale entries easily)<br/> 2.Create Networks on openstack controller<br/> 3.Spawn VM-1 on openstack controller node (i.e openstack controller node also act as compute node),check the br-int OF entries<br/> 4.Spawn VM-2 on openstack compute node),check br-int OF entries on both openstack controller and compute node.<br/> 5.Unstack &amp; cleanup the compute node instance(where VM2 node spawned).Check the br-int OF entries on openstack-controller node side.<br/> 6.stack the compute node and spawn the VM-3 (and attach step3 created network).Verify the br-int OF entries on openstack controller &amp; compute node .<br/> 7.You can see the OF stale entries br-int of openstack controller.Each VM instance(spawned on compute node) will create one OF entry on openstack controller node br-int.So OF stale entries will grow,if number of VM grows on compute node side and overload the openstack controller.</p> <p>This complete br-int OF entries captured and attached with defects.</p> <p>On Practical scenario,<br/> =====================<br/> 1.Openstack Compute node stack/unstack is common beahviour in datacenter.<br/> 2.Openstack Controller node cannot be unstacked too often,(i.e on each openstack Compute node unstack).<br/> 3.if OF stale entries doesn't cleaned on Controller node of each Compute node unstack &amp; clean side,then easily overload/exhaust the Openstack controller node OVS flow table using ODL controller.</p> <p> As per the bug, a VM is created in each of the compute nodes. When the unstack.sh script is executed only the openstack services are disabled. The VM and the network are not deleted. </p> <p> When a VM/network is deleted from openstack, 2 types of event will reach ODL,<br/> 1. Northbound events from openstack<br/> 2. South bound events from OVS </p> <p> Only after processing these 2 types of event, the ODL will clear the flows. When the unstack.sh scripts is executed on any node, the northbound events are not generated. This event will be generated by the openstack and that's the reason for flows not getting removed. The proper cleanup has to be initiated from openstack. </p> <p> The unstack.sh procedure will put ODL in a inconsistent state with respect to the flows. So, ODL cannot do anything to fix this issue. This bug will be more appropriate in openstack context.</p> <p> When the unstack.sh script is run the neutron PORT DELETE southound events does not reach ODL controller. This is the reason why the stale entries are present in controller node.<br/> When the same cleanup is done through the openstack, the neutron PORT DELETE southbound events reach the ODL controller which clears the flows in all the connected nodes.</p> <p> So, unstack.sh will not be the clean way to removes VM's and network.</p> <p> The clean way to cleanup the node is to delete VM and network from openstack Horizon UI. In this way stale entry issue can be resolved. Cleanup from openstack is the preferred approach. </p> <p> So, could you please close the BUG?</p> <p>Fixed the plugin.sh scipt to delete all the ports and then delete the OVSDB connection.</p> <p>Attachment plugin.sh has been added with description: The modified Plugin.sh will solve the stale entry issue</p> <p>1.Copied the plugin.sh (attached this bugzilla)on /opt/stack/networking-odl/devstack/<br/> 2.Restacked the compute node<br/> 3.Spwaned VM1 on compute node1 and VM2 on compute node2</p> <p>Compute node1 snip<br/> ==================<br/> sudo ovs-ofctl -O OpenFlow13 dump-flows br-int | grep "x427"</p> <p>cookie=0x0, duration=311.991s, table=110, n_packets=5, n_bytes=968, tun_id=0x427,dl_dst=fa:16:3e:94:dd:6c actions=output:3</p> <p>4.Unstacked the compute node-2 and vm-2 related OF entries has been removed from br-int</p> <p>This bug fix specific with *<b>Openstack</b>* side .Hence closing this issue.</p> <p>This BUG is specific to openstack. Submitted a review in openstack<br/> <a href="https://review.openstack.org/#/c/228393" class="external-link" target="_blank" rel="nofollow noopener">https://review.openstack.org/#/c/228393</a></p> Development External issue ID 4229 External issue URL Rank 0|i0219j: