[BGPCEP-830] Odl doesn't remove l3vpn route after receiving route-target argument Created: 25/Sep/18 Updated: 21/Nov/18 Resolved: 21/Nov/18 |
|
| Status: | Verified |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | Neon, Fluorine SR1 |
| Fix Version/s: | Neon, Fluorine SR1 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Dasa Simkova | Assignee: | Claudio David Gasparini |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
configure.py
play.py
remove_route_from_play2.py
send_route_from_play1.py
send_route_from_play2.py
start_play1.sh
start_play2.sh
|
| Description |
|
Overview: Send route-target route with specific rt argument from previous route from external peer 2. Route l3vpn is present on peer 2 in adj-rib-out. Remove route-target route from odl by sending specific rt argument from peer 2. Expect odl to remove the l3vpn route from peer 2 with update message, and also from adj-rib-out.
Steps to reproduce: feature:install odl-restconf odl-bgpcep-bgp odl-bgpcep-bgp-config-example 2. Configure ebgp peer 1 with 127.0.0.2 IP and 1 ibgp peer 2 with 127.0.0.3 IP ./configure.py 3. Start play.py's ./start_play1.sh ./start_play2.sh 4. Send l3vpn route from first play, and than route-target route from second play ./send_route_from_play1.py ./send_route_from_play2.py 5. Remove route-target route from odl by sending specific rt argument from peer 2. ./remove_route_from_play2.py |
| Comments |
| Comment by Claudio David Gasparini [ 09/Oct/18 ] |
|
DasaSimko Could you close the bug once you review is solved? also if you call send*play2.py and then remove*play2.py You will see that there is a bug under remove patch. Points to wrong port
|