BGPaaS: v6 instance IP should not be set as local BGP IP

Bug #1543713 reported by amit surana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
Medium
Suresh Balineni

Bug Description

If an IP address is not explicitly configured on the BGPaaS object, one of the primary instance IPs attached to the VMI is chosen as the local IP address. This IP address is used to source the BGP session from the VM. If the VN is dual stack (v4/v6 cidr), then schema should pick one of the configured v4 instance IPs, and not the v6 IP.

Tags: bgpaas config
amit surana (asurana-t)
summary: - BGPaaS: Loacal IP address should be set to v4 instance IP
+ BGPaaS: v6 instance IP should not be set as local BGP IP
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/17099
Submitter: Sachin Bansal (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/17099
Committed: http://github.org/Juniper/contrail-controller/commit/c126f398ca83f792b8c1cba33510b294fe139456
Submitter: Zuul
Branch: master

commit c126f398ca83f792b8c1cba33510b294fe139456
Author: Sachin Bansal <email address hidden>
Date: Tue Feb 9 17:45:21 2016 -0800

Don't pick v6 ip address for BGPaaS clients

Don't select a v6 address while picking address for BGPaaS because it is not supported by the back end.
Also, don't create default-bgp-as-a-service object

Closes-Bug: 1543713
Closes-Bug: 1543715

Change-Id: I85abefb812efc8818641935e6e57cb77f3b1f1d6

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.