Avoid having an RT multiple times in an RPC
Bug #1719589 reported by
Thomas Morin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BaGPipe |
Fix Released
|
Low
|
Unassigned | ||
networking-bgpvpn |
Fix Released
|
Undecided
|
Cedric Savignan |
Bug Description
The bagpipe driver for BGPVPN compiles the BGPVPN route_targets, import_targets, export_targets attibutes into one "import RTs" list and one "export RTs" list. The "import RTs" list contains the RT from route_targets and import_targets, and the "export RTs" list contains the RT from route_targets and export_targets.
Currently, the code [1] does not filter duplicates: e.g. an RT that is both in route_targets and import_targets will be present twice in the RPCs between neutron server and agents, and agents will also pass this RT twice to bagpipe-bgp.
It would be better to avoid this duplicate.
Changed in networking-bagpipe: | |
importance: | Medium → Low |
Changed in networking-bagpipe: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/513670
Review: https:/