Default route not advertised into VN via Route-Agrgregate config

Bug #1545125 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
High
Nischal Sheth

Bug Description

Even though a route-aggregate object with route prefix 0.0.0.0/0 has been attached to the service instance, the default route isn't advertised into the VN. If the route prefix is changed to 0.0.0.0/1 the aggregate is generated correctly and other more specific routes are suppressed.

amit surana (asurana-t)
tags: added: blocker
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/17203
Submitter: Nischal Sheth (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Review in progress for https://review.opencontrail.org/17218
Submitter: Prakash Bailkeri (<email address hidden>)

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

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

commit c0e3dae3732a212b4a075e68da1dec4939554adf
Author: Nischal Sheth <email address hidden>
Date: Fri Feb 12 11:42:02 2016 -0800

Fix aggregation for inet default route prefix

Highlights:

- Fix root cause in InetPrefix::IsMoreSpecific
- Add unit tests for InetRoute and RouteAggregator

Change-Id: I2d06a6a300f34c95bade81dfaafd2e153a39cab1
Closes-Bug: 1545125

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.