Configure RD with wrong format is allowed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-bgpvpn |
Fix Released
|
High
|
Thomas Morin | ||
Juno |
Confirmed
|
High
|
Unassigned | ||
Kilo |
Confirmed
|
High
|
Unassigned | ||
Liberty |
Fix Released
|
High
|
Thomas Morin |
Bug Description
juno@ubuntu:
Created a new bgpvpn:
+------
| Field | Value |
+------
| auto_aggregate | True |
| export_targets | |
| id | 1f2d29ce-
| import_targets | |
| name | juno |
| networks | |
| route_distingui
| route_targets | 100:0 |
| routers | |
| tenant_id | 6c557bea9025437
| type | l2 |
+------
The RD format must be AA:NN or IP:NN, so 100 should not be allowed
Changed in bgpvpn: | |
milestone: | none → liberty |
no longer affects: | bgpvpn/trunk |
Based on the show command above the bug looks valid.
It is surprising though : there is code (extension/ bgpvpn. py) to validate route-targets and route-distingui shers, and the test case confirms that it works for route-targets.