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/OPNFLWPLUG-467 OpenFlowPlugin <p>Group id's corresponding to the LAG entry isn't removed on removing the LAG entry. Issue seen with the latest integration image(1901 build).</p> <p>On querying the node specific RESTAPI after bringing down the LAG group, the lacp specific tag are not displayed, but then the group-id which which the LAG has used is still retained.</p> <p>Operating System: Linux<br/> Platform: All</p> OPNFLWPLUG-467

Group id's aren't removed from the node when the corresponding LAG entry is removed

Bug Verified Done Mahesh Manivasagam Mahesh Manivasagam Thu, 28 May 2015 05:53:11 +0000 Mon, 27 Sep 2021 09:01:33 +0000 Fri, 26 Jun 2015 10:17:19 +0000 General 0 4 <p>Attachment restapi.txt has been added with description: RESTAPI o/p</p> <p>Please find the show dump-flows o/p prior and after lag removal. Entries are still present under the REST API node specific o/p.</p> <p>mininet&gt; sh ovs-ofctl -O Openflow13 dump-groups s6<br/> OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):<br/> group_id=21429,type=select,bucket=weight:0,actions=output:1,output:2<br/> group_id=60520,type=all,bucket=weight:0,actions=group:21429</p> <p>mininet&gt; sh ovs-ofctl -O Openflow13 dump-groups s6<br/> OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):<br/> group_id=60520,type=all,bucket=weight:0,actions=drop</p> <p>On removing the LAG interface, for the group entry corresponding to the LAG, the removeGroup API available in the SalGroupService interface is invoked.<br/> Also, the asynchronous output of the API returns success value.<br/> The Group entry (with group id 21419) is removed from the openflow enabled switch by the remove Group API. (dump-groups output is also provided)</p> <p>But the group table entry information (for the removed group) is retained in the MD-SAL datastore. And this is displayed in the REST output invoked for the corresponding node.<br/> This seems like DataStore retains the stale information of the group table entry.</p> <p>It is not possible to replicate this issue on current stable/lithium branch. After removing group from mininet it was removed from operational datastore as well.</p> <p>Hi Martin,</p> <p>I've verified the above issue on the latest build stable/lithium branch and was not able to recreate this problem. Please move this bug to resolved state.</p> <p>Moving this bug to verified state as its no longer re creatable with the latest stable lithium branch</p> Development External issue ID 3405 External issue URL Issue Type ODL SR Target Milestone Rank 0|i031bz: