[NETVIRT-1199] Wrong VRF-ID is populated for extra route VPN Interface Adjacency Created: 09/Apr/18  Updated: 14/May/18  Resolved: 12/Apr/18

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

Type: Bug Priority: Low
Reporter: Karthikeyan Krishnan Assignee: nithi thomas
Resolution: Won't Do Votes: 0
Labels: VPNV6
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Wrong "vrf-id" is populated for extra route VPN Interface Adjacency. Currently It is populated with DPN-ID as vrf-id which is wrong.

CSIT Recent Log Ref Link:

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-openstack-queens-gate-stateful-fluorine/193/robot-plugin/log_full.html.gz

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-openstack-queens-gate-stateful-fluorine/193/robot-plugin/log_full.html.gz#s1-s8-t10-k21-k2-k1-k2-k52-k3

Example Output:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-openstack-queens-gate-stateful-fluorine/193/robot-plugin/log_full.html.gz#s1-s8-t10-k21-k2-k1-k2-k52

restconf/operational/odl-l3vpn:vpn-interface-op-data

{
"adjacency": [

{ "adjacency_type": "extra-route", "ip_address": "2001:db9:cafe:d::/64", "label": 100385, "next-hop-ip-list": [ "2001:db8:0:2:f816:3eff:fe97:5d18" ], "phys-network-func": false, * "vrf-id": "185774449107796" (Wrong Value)* }

,

{ "adjacency_type": "primary-adjacency", "ip_address": "2001:db8:0:2:f816:3eff:fe97:5d18/128", "label": 100381, "mac_address": "fa:16:3e:97:5d:18", "next-hop-ip-list": [ "10.30.170.63" ], "phys-network-func": false, "subnet_id": "f7ff7a68-086c-4057-ba24-ca55210e7c87", * "vrf-id": "694f61f1-75ac-4236-9ca8-b0696d9352ad" (Correct Value)* }

,

Steps to reproduce the issue:
Please refer the below CSIT ref link TC ( Add Multiple Extra Routes And Check Datapath Before L3VPN Creation)
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-openstack-queens-gate-stateful-fluorine/193/robot-plugin/log_full.html.gz#s1-s8-t10

 Comments   
Comment by nithi thomas [ 12/Apr/18 ]

For  static routes while attaching to a router , dpn-id is taken in consideration with ecmp case for load-balancing . router-id will not distinguish the static routes from which dpn it is generated.

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