VNF route did not appear in fib/flows due to interface manager did not update the parentref

Description

We found during our testing that when ever there is a reboot of the ODL, some of the neutron port interface state was not available for the other services(L3VPN).

below is the analysis of the problem.

We root-caused the problem to parentRef not set in Interface-Config DS for the port 794e9449-933c-4412-8b88-c27e2b2ec8f7.

Because parentRef is not set, interfaceState was not created for 794e9449-933c-4412-8b88-c27e2b2ec8f7, which resulted in that interface not being processed by both ELAN and L3VPN.

When I analyzed further why parentRef is not set, it looked to me that an update() call in NeutronPortChangeListener never got fired . However, from the log files we noticed two add() invocations in the NeutronPortChangeListener which is tagged to Neutron-Port entity of Config DS.

Environment

None

Activity

Show:

karthikeyan Krishnan February 12, 2020 at 11:47 AM

karthikeyan Krishnan February 12, 2020 at 11:46 AM

Please refer the below gerrit link for confirmed fix for reported issue.

https://git.opendaylight.org/gerrit/#/c/netvirt/+/87371/

Done

Details

Assignee

Reporter

Time tracking

3d logged

Components

Fix versions

Priority

Created February 3, 2020 at 6:33 AM
Updated February 12, 2020 at 11:47 AM
Resolved February 12, 2020 at 11:45 AM