Re: [openflowplugin-dev] openflowplugin blocker bug

Thanks Vishal – giving that I assume we should consider using this as a workaround in SR2 (should probably run verifications first) Thanks, Koby From: Vishal Thapar [mailto:vishal.tha...@ericsson.com] Sent: Thursday, December 15, 2016 7:54 AM To: Aizer, Koby ; Abhijit

Re: [openflowplugin-dev] openflowplugin blocker bug

Hi Koby, Sorry for delayed response, it was rather late at night for me. This listener is only interested in Group entries configured by Elan i.e. Config DataStore. Statistics code is for populating operational DS which we’re not using today in any of netvirt code. Regards, Vishal. From:

Re: [openflowplugin-dev] openflowplugin blocker bug

Vishal, Just to make sure I understand - Are you saying there is non-statistics related code that also creates those group entries? Because I can see the ElanGroupListener code is listening on these (relatively new code, 13 days ago) Thanks, Koby From: Vishal Thapar

Re: [openflowplugin-dev] openflowplugin blocker bug

No, we don’t have dependency on stats in L2GW or any genius/netvirt code, yet ☺ Regards, Vishal. From: Aizer, Koby [mailto:koby.ai...@hpe.com] Sent: 15 December 2016 02:49 To: Abhijit Kumbhare ; Shuva Jyoti Kar Cc: Kochba, Alon

Re: [openflowplugin-dev] openflowplugin blocker bug

+ netvirt-dev So far we weren’t able to reproduce the issue when statistics are disabled (still undergoes testing), but I’m not sure what effects it might have on the netvirt/genius code. I’ve seen some Flow & Group listeners in genius/netvirt (If I understand correctly

Re: [openflowplugin-dev] openflowplugin blocker bug

Hi Alon, As discussed with Koby over IRC today, with statistics turned off we mightnot see this issue. As I understand netvirt doesnot(as of now depend much on OfPlugin statistics) hence with stats off if the issue is not reproduced, I think we can consider that to be a valid workaround for

Re: [openflowplugin-dev] openflowplugin blocker bug

Hi Abhijit, I commented on the bug [1]. This bug is very problematic in that it leaves the DPN unusable, though it appears as available so VMs are allocated to it. It has been encountered several times and reproduction details/info was provided, would appreciate your feedback on the bug itself.

Re: [openflowplugin-dev] openflowplugin blocker bug

Anil’s proposed change has been merged on stable/boron. 6908 might require a few more cycles, since with only openflowplugin and no other applications, I do not see any problem in bringup of ports. Would require some help from netvirt also to understand the problem. Thanks, -shuva From:

Re: [openflowplugin-dev] openflowplugin blocker bug

Thanks Luis. On Monday, December 12, 2016, Luis Gomez wrote: > Well, I guess this is kind of similar to bug 6575, it is blocker because > this is a regression from Beryllium release (old plugin). But the issue > (report alien ID instead of normal ID in operational) does not

Re: [openflowplugin-dev] openflowplugin blocker bug

Well, I guess this is kind of similar to bug 6575, it is blocker because this is a regression from Beryllium release (old plugin). But the issue (report alien ID instead of normal ID in operational) does not impact dataplane forwarding + it does not happen with all flows (it took me some time

Re: [openflowplugin-dev] openflowplugin blocker bug

About https://bugs.opendaylight.org/show_bug.cgi?id=6917 - I understand the following: The fix for this was https://git.opendaylight.org/gerrit/#/c/47138/ (master) and https://git.opendaylight.org/gerrit/#/c/47320 (stable/boron). The fix caused more issues & instabilities which was a blocker.

Re: [openflowplugin-dev] openflowplugin blocker bug

If I am not mistaken - I think Anil had backed out the following change: https://bugs.opendaylight.org/show_bug.cgi?id=6917. Not sure if it got merged Anil? About https://bugs.opendaylight.org/show_bug.cgi?id=6908 - added Alon (as he has raised the priority to blocker yesterday). Alon - would

[openflowplugin-dev] openflowplugin blocker bug

Hi OPENFLOWPLUGIN Team, We would like to kindly request an update on these OPENFLOWPLUGIN Boron Blocker Bugs? Please let us know the ETA for a fix or if we should retarget the blocker bug for Boron-SR3 instead. Bug 6908 - failed to update port status - all new OVS ports fail from this point.

Re: [openflowplugin-dev] openflowplugin blocker bug

; openflowplugin-dev@lists.opendaylight.org Subject: Re: [openflowplugin-dev] openflowplugin blocker bug Hi An, I didn't get time to work on the bug. I request to carry forward it to SR3. On Thu, Dec 1, 2016 at 9:49 AM, An Ho <an...@huawei.com<mailto:an...@huawei.com>> wrote:

Re: [openflowplugin-dev] openflowplugin blocker bug

Hi An, I didn't get time to work on the bug. I request to carry forward it to SR3. On Thu, Dec 1, 2016 at 9:49 AM, An Ho wrote: > Hi L2SWITCH and OPENFLOWPLUGIN Team, > > We would like to kindly request an update on this OPENFLOWPLUGIN/L2SWITCH > Boron Blocker Bug? Please

Re: [openflowplugin-dev] openflowplugin blocker bug

Severity: By default stats collection is on. So this issue will not occur. But with statistics turned off before a switch connection, flow provisioning is not going through. And that breaks the ofplugin functionality Testing: end to end testing done by individuals with 2-5 flows, multiple times