[BGPCEP-769] Extra path-id argument on fluorine l3vpn Created: 19/Mar/18  Updated: 05/Apr/18  Resolved: 05/Apr/18

Status: Verified
Project: bgpcep
Component/s: BGP
Affects Version/s: Fluorine
Fix Version/s: Fluorine

Type: Bug Priority: Medium
Reporter: Tomas Markovic Assignee: Tomas Markovic
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File exabgpl3vpn.cfg     File reconf.py    

 Description   

In userfeatures this test 010_Bgp_Functional_L3Vpn fails due to additional argument in output.

It's in effective-rib-in and loc-rib but not in adj-rib-in on FLUORINE
on O2 it's not present at all

 "label-value": 24005 } ],
+ "path-id": 0,
"prefix": "1.1.1.0/24",
"route-distinguisher": "1.2.3.4:1",
"route-key": "WAABAQIDBAABAQEB"

Steps to reproduce
1)Run bin/karaf (fluorine)
2)Install>
feature:install odl-restconf
feature:install odl-bgpcep-bgp
feature:install odl-bgpcep-bgp-config-example
3)run

./reconf.py

4)run exabgp with

env exabgp.tcp.port=1790 exabgp --debug exabgpl3vpn.cfg

5)check full rib output with

curl -H "Accept: application/json" -u admin:admin "http://localhost:8181/restconf/operational/bgp-rib:bgp-rib/rib/example-bgp-rib"

See the

"path-id"

extra argument

It is not present in oxygen, therefore the current test verification fails.

Let me know if it is there to stay, so I can adjust data.json against which it is compared.



 Comments   
Comment by Claudio David Gasparini [ 20/Mar/18 ]

https://git.opendaylight.org/gerrit/#/q/topic:BGPCEP-769+(status:open+OR+status:merged)

Comment by Claudio David Gasparini [ 03/Apr/18 ]

Additional path will  be compatible with all families, therefore this path-id must be present since now.

Please update test for all families, where is not present.

Comment by Tomas Markovic [ 05/Apr/18 ]

https://git.opendaylight.org/gerrit/#/c/70323/
https://git.opendaylight.org/gerrit/#/c/70335/
https://git.opendaylight.org/gerrit/#/c/70320/

Generated at Wed Feb 07 19:14:04 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.