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-667 OpenFlowPlugin <p>Group Reconciliation fails on a controller node restart with ovs2.3.2 switch</p> <p>Steps to reproduce:</p> <p>1. Configure a group(either FF/Indirect/ALL/SELECT) on the controller using POSTMAN</p> <p>2. Connect an ovs2.3.2 switch. The switch reflects the flow due to reconciliation</p> <p>3. Start the wireshark on the 6633 port and Restart the controller</p> <p>4. We see OFPGMFC_GROUP_EXISTS error for the group_mod on the wire. </p> <p>On analysing the issue, it happens due to the fact that by the Openflow specifications(both 1.3.1 and 1.3.5):</p> <p>"For add requests (OFPGC_ADD), if a group entry with the specified group identifier already resides in<br/> the group table, then the switch must refuse to add the group entry and must send an ofp_error_msg<br/> with OFPET_GROUP_MOD_FAILED type and OFPGMFC_GROUP_EXISTS code."</p> <p>(pg 37/47)</p> <p>Operating System: Other<br/> Platform: Other</p> OPNFLWPLUG-667

Group reconciliation fails during Controller Restart with ovs2.3.2

Bug Medium Resolved Done Anil Vishnoi Shuva Jyoti Kar Sat, 2 Apr 2016 14:56:30 +0000 Mon, 27 Sep 2021 09:01:47 +0000 Thu, 2 May 2019 00:46:57 +0000 Fluorine-SR2 Neon General 0 4 <p>please apply the following filter openflow_v4.type == 15 or look at packets 182,184,186,188,192,194,</p> <p>Attachment Bug5646.pcapng has been added with description: wireshark capture of the packets during controller restart</p> <p>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?</p> <p>No we dont react to the error message as of now</p> <p>We will need to have Shuva update this bug.</p> <p>Shuva - any updates on this?</p> Duplicate OPNFLWPLUG-788 Development External issue ID 5646 External issue URL Rank 0|i032kf: