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 to write 
the automation to reproduce it), so I believe we can lower down the priority to 
CRITICAL and target it for Boron SR3 if nobody has objections.

BR/Luis


> On Dec 12, 2016, at 6:35 PM, Abhijit Kumbhare <abhijitk...@gmail.com> wrote:
> 
> About  https://bugs.opendaylight.org/show_bug.cgi?id=6917 
> <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/ 
> <https://git.opendaylight.org/gerrit/#/c/47138/> (master) and 
> https://git.opendaylight.org/gerrit/#/c/47320 
> <https://git.opendaylight.org/gerrit/#/c/47320> (stable/boron). The fix 
> caused more issues & instabilities which was a blocker. That fix has been 
> taken out by Jozef - which leaved 6917. However that is not a blocker. Luis 
> should confirm and reduce the priority of 6917.  
> 
> 
> On Mon, Dec 12, 2016 at 6:04 PM, Abhijit Kumbhare <abhijitk...@gmail.com 
> <mailto:abhijitk...@gmail.com>> wrote:
> If I am not mistaken - I think Anil had backed out the following change: 
> https://bugs.opendaylight.org/show_bug.cgi?id=6917 
> <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 
> <https://bugs.opendaylight.org/show_bug.cgi?id=6908> - added Alon (as he has 
> raised the priority to blocker yesterday).
> 
> Alon - would like to check with you if you think it is OK to defer this bug 
> (6908) to the next SR since we need to get this SR out and the 
> investigation/fix by Shuva/Jozef may need a few days? 
> 
> On Mon, Dec 12, 2016 at 5:20 PM, An Ho <an...@huawei.com 
> <mailto:an...@huawei.com>> wrote:
> 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.  Is this only for Carbon or does it apply to Boron-SR2 as well?  
> Otherwise, we should retarget for Carbon.
> Bug 6917 - Flow matching function (operational flow reconciliation) is not 
> stable.  Luis reopened this bug on 12/08.  Are there plans to fix it now, or 
> can we retarget for Boron-SR3 for more time?
> 
> Best Regards,
> An Ho
> 
> [1] https://bugs.opendaylight.org/show_bug.cgi?id=6908 
> <https://bugs.opendaylight.org/show_bug.cgi?id=6908>
> [2] https://bugs.opendaylight.org/show_bug.cgi?id=7343 
> <https://bugs.opendaylight.org/show_bug.cgi?id=7343>
> 
> 
> 

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to