VNF route did not appear as no parentrefs 71/87371/3
authorKarthikeyan Krishnan <karthikeyan.k@altencalsoftlabs.com>
Mon, 3 Feb 2020 08:33:07 +0000 (14:03 +0530)
committerKarthikeyan Krishnan <karthikeyangceb007@gmail.com>
Tue, 11 Feb 2020 06:01:40 +0000 (06:01 +0000)
commit2300ef30e455ac1f1546567c3fc4d29e7f1d2180
treef561c75a8bfc6fff5667554d8d335085e52ac395
parentac6c7ea166223e35fa5a654f0f39dc609daa0708
VNF route did not appear as no parentrefs

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

Solution:
==========
We are not updating parentrefs for VM interfaces via
northbound calls, but rather via southbound events through
InterfaceManager.
Hence, any missed events for port updates also need not update the
parentrefs.

Signed-off-by: Karthikeyan Krishnan <karthikeyangceb007@gmail.com>
Change-Id: I4824579e997f3fb18033f73d120a8d8dd65024c3
neutronvpn/impl/src/main/java/org/opendaylight/netvirt/neutronvpn/NeutronPortChangeListener.java