[NETVIRT-452] Vpn Interface not deleted from operational data store Created: 31/Jan/17  Updated: 18/Apr/17  Resolved: 18/Apr/17

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug
Reporter: Olga Schukin Assignee: Olga Schukin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File clean_vpn_intf_issue_karaf.rar    
Issue Links:
Duplicate
is duplicated by NETVIRT-621 After network dissociate & associate ... Resolved
External issue ID: 7714

 Description   

Vpn Interface not deleted from operational/l3vpn:vpn-interfaces model, if there is more than one adjacency to this vpn interface.
This could happen because adjacency is deleted using Future callback.

Example: look for 72bf5a20-400b-3e08-952b-ab174e6bc661 or a6d4bd82-ddbc-3698-9afc-9c602c6bbcd4 in the attached log

 Comments   
Comment by Olga Schukin [ 31/Jan/17 ]

Attachment clean_vpn_intf_issue_karaf.rar has been added with description: log

Comment by Olga Schukin [ 31/Jan/17 ]

Review: https://git.opendaylight.org/gerrit/51224

Comment by Konstantin Pozdeev [ 01/Mar/17 ]

The current resolution depends on order of deletion of VrfEntry and delete listener execution.
If VrfEntry for primary adjacency is deleted before secondary, the interface will stuck in operational DB.
Deletion of VrfEntry is performed by one transaction and order of listener execution is unpredictable.

Comment by Vivekanandan Narasimhan [ 02/Mar/17 ]

I have raised a review for this:
https://git.opendaylight.org/gerrit/52655

Comment by Vivekanandan Narasimhan [ 02/Mar/17 ]

With current available information within CleanUpVpnInterfaceWorker, we cannot reliably remove the vpn Interface for the reverse ordering (like extra-route prefix deleted first, followed by primary prefix deleted next).

However, the most typical order is for primary prefix getting deleted first, followed by extra-route prefixes. Atleast this typical order used to work before this patch broke it: https://git.opendaylight.org/gerrit/51224

Now the new patch fixes the breakage:
https://git.opendaylight.org/gerrit/#/c/52655

Generated at Wed Feb 07 20:21:35 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.