Do not advertise L2 addresses if VN is configured to be L3 only
Bug #1564724 reported by
Nischal Sheth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
Medium
|
Manish Singh | |||
Trunk |
Fix Committed
|
Medium
|
Manish Singh |
Bug Description
Agent should not advertise L2 addresses to CN if VN is configured with
forwarding mode L3 only. Both unicast and broadcast routes should not
be advertised.
Doing this avoids exercising unnecessary code in CN and reduces number
of routes in the system. It is expected that Kubernetes will create L3
only networks by default.
Agent should continue to process any L2 routes received from CN. This
is required for correctness when forwarding mode transitions from L3 to
L2+L3.
Review in progress for https:/ /review. opencontrail. org/21500
Submitter: Manish Singh (<email address hidden>)