Uploaded image for project: 'netvirt'
  1. netvirt
  2. NETVIRT-1667

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Magnesium
    • None
    • neutronvpn
    • None

      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.

            Karthikeyan Karthikeyan Krishnan
            Karthikeyan Karthikeyan Krishnan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days
                3d