v2 SvcTmpl: ecmp doesnt work if service vm instances are in same compute
Bug #1546958 reported by
Senthilnathan Murugappan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Manish Singh | |||
R2.21.x |
Fix Committed
|
High
|
Manish Singh | |||
R2.22.x |
Fix Committed
|
High
|
Manish Singh | |||
R3.0 |
Fix Committed
|
High
|
Manish Singh | |||
Trunk |
Fix Committed
|
High
|
Manish Singh |
Bug Description
Build: 3.0-2713 kilo
Using Service Template v2 created two instances(
Both the service vms were launched on the same compute node.
Observed that in which case agent doesnt have ecmp nh for the imported routes rather nh is empty(/drop).
FYI, the control node has the correct ecmp nh for the imported routes in the left vn.
tags: | added: service-chain vrouter |
To post a comment you must log in.
If mpls label points to composite next hop, agent crosschecks if the next hop key
enqueued from controller route import context and the next hop key mpls label
points to in operDB are same. The check for crosschecking the same was wrong.