In my opinion, it's not really a functionality regression. Because
previously this value was set to 10 second and if setting up slave role to
the device fails in the 10 second, it will retry after some timeout, so
that scenario can also lead to the similar situation where setting slave
role takes more then 20 second. But setting up 20 second of a delay by
default is a way too high and  can cause lot of issues, so we should move
away from this.

On Thu, Jul 6, 2017 at 9:03 AM, Luis Gomez <[email protected]> wrote:

> Yes but I am not 100% sure this was fully working before so I cannot
> really tell this is a blocker...
>
> > On Jul 6, 2017, at 8:58 AM, Jamo Luhrsen <[email protected]> wrote:
> >
> > ok. if it's a regression, we may want to consider it a blocker?
> >
> > On 07/06/2017 08:57 AM, Luis Gomez wrote:
> >> I am not sure, it could be a regression introduced by the new 20 secs
> slave connection waiting.
> >>
> >>> On Jul 6, 2017, at 8:55 AM, Jamo Luhrsen <[email protected]> wrote:
> >>>
> >>> Is it a regression or just newly discovered?
> >>>
> >>> JamO
> >>>
> >>> On 07/06/2017 08:48 AM, Luis Gomez wrote:
> >>>> FYI yesterday we merged a patch in int/test that will give stability
> to OF cluster test:
> >>>>
> >>>> https://git.opendaylight.org/gerrit/#/c/59956/
> >>>>
> >>>> However by doing the patch I realized about this critical bug in
> Carbon:
> >>>>
> >>>> https://bugs.opendaylight.org/show_bug.cgi?id=8805
> >>>>
> >>>> BR/Luis
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> openflowplugin-dev mailing list
> >>>> [email protected]
> >>>> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >>>>
> >>
>
> _______________________________________________
> openflowplugin-dev mailing list
> [email protected]
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>



-- 
Thanks
Anil
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to