Static routes stuck in dormant state (interface discovery broken?)

[Kenth Eriksson]

On Tue, 2018-09-18 at 19:45 +0200, Ondrej Zajicek wrote:
> CAUTION: This email originated from outside of the organization. Do
> not click links or open attachments unless you recognize the sender
> and know the content is safe.
> 
> 
> On Tue, Sep 18, 2018 at 07:34:03PM +0200, Ondrej Zajicek wrote:
> > > Looks broken in 2.0.2. Can you retest on 2.0.2 as well?
> > 
> > You are right, it is broken on 2.0.2, it is fixed by patch:
> > 
> > 586c1800c447ff099d34889b23647c4733876d9b
> > Nest: Neighbor cache cleanups
> 
> So it is likely specific to interface neighbor cache entries (which
> are
> used by static protocol), general interface discovery / notifications
> should work fine.

I can confirm that 586c1800c447ff099d34889b23647c4733876d9b cherry-
picked on top of 2.0.2 works as well.

Are you planning a 2.0.3 any time soon to address this issue? We could
make use of that.

Thanks,
Kenth