[OPNFLWPLUG-667] Group reconciliation fails during Controller Restart with ovs2.3.2 Created: 02/Apr/16  Updated: 27/Sep/21  Resolved: 02/May/19

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: Fluorine-SR2, Neon

Type: Bug Priority: Medium
Reporter: Shuva Jyoti Kar Assignee: Anil Vishnoi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Other
Platform: Other

Attachments: File Bug5646.pcapng    
Issue Links:
Duplicate
duplicates OPNFLWPLUG-788 Support for OFPGC11_ADD_OR_MOD Resolved
External issue ID: 5646

 Description   

Group Reconciliation fails on a controller node restart with ovs2.3.2 switch

Steps to reproduce:

1. Configure a group(either FF/Indirect/ALL/SELECT) on the controller using POSTMAN

2. Connect an ovs2.3.2 switch. The switch reflects the flow due to reconciliation

3. Start the wireshark on the 6633 port and Restart the controller

4. We see OFPGMFC_GROUP_EXISTS error for the group_mod on the wire.

On analysing the issue, it happens due to the fact that by the Openflow specifications(both 1.3.1 and 1.3.5):

"For add requests (OFPGC_ADD), if a group entry with the specified group identifier already resides in
the group table, then the switch must refuse to add the group entry and must send an ofp_error_msg
with OFPET_GROUP_MOD_FAILED type and OFPGMFC_GROUP_EXISTS code."

(pg 37/47)

 Comments   
Comment by Shuva Jyoti Kar [ 02/Apr/16 ]

please apply the following filter openflow_v4.type == 15 or look at packets 182,184,186,188,192,194,

Comment by Shuva Jyoti Kar [ 02/Apr/16 ]

Attachment Bug5646.pcapng has been added with description: wireshark capture of the packets during controller restart

Comment by Anil Vishnoi [ 04/Apr/16 ]

I think that's expected behavior and we should ignore the error message if it's OFPGMFC_GROUP_EXISTS. BTW, do we react to the error message?

Comment by Shuva Jyoti Kar [ 05/Apr/16 ]

No we dont react to the error message as of now

Comment by Abhijit Kumbhare [ 30/Oct/17 ]

We will need to have Shuva update this bug.

Comment by Abhijit Kumbhare [ 27/Nov/17 ]

Shuva - any updates on this?

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