using ip-addr:asn format for router_distinguisher throws Invalid input error

Bug #1557588 reported by Vishal Thapar
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
networking-bgpvpn
Fix Released
Medium
Thomas Monguillon

Bug Description

As per the spec <4-byte IPv4>:<16-bit-number> is a valid format for Route Target and/or Route Distinguisher, but trying to create a bgpvpn with such a RD throws Invalid Input error:

:~/devstack$ neutron bgpvpn-create --name vpn3 --route-distinguishers 12.1.1.1:11
Invalid input for route_distinguishers. Reason: '12.1.1.1:11' is not a valid input.

Changed in bgpvpn:
status: New → Confirmed
importance: Undecided → Medium
Changed in bgpvpn:
milestone: none → 5.0.0
Changed in bgpvpn:
assignee: nobody → Thomas Monguillon (thomas-monguillon)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-bgpvpn (master)

Reviewed: https://review.openstack.org/331159
Committed: https://git.openstack.org/cgit/openstack/networking-bgpvpn/commit/?id=7b3a06e883e45c4252d70c62591e512d12427627
Submitter: Jenkins
Branch: master

commit 7b3a06e883e45c4252d70c62591e512d12427627
Author: Thomas Monguillon <email address hidden>
Date: Fri Jun 17 16:04:03 2016 +0200

    Fix RD regex to match RFC 4364, chapter 4.2

    Improve test for invalid RTs and invalid RDs (Add type 1 and Type 2 formats)

    Add test for valid RTs and valid RDs

    Closes-Bug: 1557588

    Change-Id: Icb7a135fc103a1ff255255ff84a90e5fc610b8ba

Changed in bgpvpn:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-bgpvpn 5.0.0

This issue was fixed in the openstack/networking-bgpvpn 5.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.