Service Instance scaling breaks the static route community logic
Bug #1549541 reported by
Ato
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
High
|
Naveen N | |||
Trunk |
Fix Committed
|
High
|
Naveen N |
Bug Description
Thanks to Amit Surana for debugging.
Static routes associated to Service Instances now have an option to set a community like no-reoriginate or no-export. The desired effect is observed in Service Instances cloned from a v1 template that does not have the scaling option checked.
On the other hand, if I try the same on a v1 Service Instance with scale-out (two instances), the community values that I set in the GUI is not causing any effect at all. For example, no-reoriginate does not prevent the route from being reoriginated; and no-export is not set in the route, as I can check in a MX.
I did not try on v2 Service Instances since the GUI is not ready yet.
tags: | added: blocker |
affects: | opencontrail → juniperopenstack |
To post a comment you must log in.
Note that both service instances are on the same agent in this case.
When we checked the agent route table we saw that the 2 LocaVmPort
paths have the configured community values. However, the Ecmp
path created by agent doesn't have any communities.