[OPNFLWPLUG-467] Group id's aren't removed from the node when the corresponding LAG entry is removed Created: 28/May/15  Updated: 27/Sep/21  Resolved: 26/Jun/15

Status: Verified
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Mahesh Manivasagam Assignee: Mahesh Manivasagam
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All

Attachments: Text File restapi.txt    
External issue ID: 3405

 Description   

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).

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.

 Comments   
Comment by Mahesh Manivasagam [ 28/May/15 ]

Attachment restapi.txt has been added with description: RESTAPI o/p

Comment by Mahesh Manivasagam [ 28/May/15 ]

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.

mininet> sh ovs-ofctl -O Openflow13 dump-groups s6
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=21429,type=select,bucket=weight:0,actions=output:1,output:2
group_id=60520,type=all,bucket=weight:0,actions=group:21429

mininet> sh ovs-ofctl -O Openflow13 dump-groups s6
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=60520,type=all,bucket=weight:0,actions=drop

Comment by Kalaiselvi [ 28/May/15 ]

On removing the LAG interface, for the group entry corresponding to the LAG, the removeGroup API available in the SalGroupService interface is invoked.
Also, the asynchronous output of the API returns success value.
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)

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.
This seems like DataStore retains the stale information of the group table entry.

Comment by Martin Bobak [ 19/Jun/15 ]

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.

Comment by Mahesh Manivasagam [ 26/Jun/15 ]

Hi Martin,

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.

Comment by Mahesh Manivasagam [ 26/Jun/15 ]

Moving this bug to verified state as its no longer re creatable with the latest stable lithium branch

Generated at Wed Feb 07 20:32:33 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.