[NETVIRT-1667] VNF route did not appear in fib/flows due to interface manager did not update the parentref Created: 03/Feb/20 Updated: 12/Feb/20 Resolved: 12/Feb/20 |
|
| Status: | Verified |
| Project: | netvirt |
| Component/s: | neutronvpn |
| Affects Version/s: | None |
| Fix Version/s: | Magnesium |
| Type: | Bug | Priority: | Medium |
| Reporter: | Karthikeyan Krishnan | Assignee: | Karthikeyan Krishnan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 3 days | ||
| Original Estimate: | Not Specified | ||
| 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. |
| Comments |
| Comment by Karthikeyan Krishnan [ 12/Feb/20 ] |
|
Please refer the below gerrit link for confirmed fix for reported issue. |
| Comment by Karthikeyan Krishnan [ 12/Feb/20 ] |
|
Please refer the below CSIT job result for QA. |