Use consistent filter API syntax

Change ID Id5d8ac09a38c656619f88a6f87b8f384fe4c55a8 introduced a
call to get_subnets, using a filter to select all subnets on a
network. The syntax for the filter in get_subnets has been to
provide a dictionary where the values are lists. The change
doesn't cause an exception because the OVO layer code handles
scalar values. Tbis commit changes the filter syntax to be
consistent.

Change-Id: Ifb9df94128b7069e78e193bc289be17e15968167
This commit is contained in:
Thomas Bachman 2021-01-17 22:34:14 +00:00
parent 56bea066f4
commit e7d126f9bc
1 changed files with 1 additions and 1 deletions

View File

@ -584,7 +584,7 @@ class L3_NAT_dbonly_mixin(l3.RouterPluginBase,
if p.get('device_owner') == DEVICE_OWNER_ROUTER_GW: if p.get('device_owner') == DEVICE_OWNER_ROUTER_GW:
ext_subts = self._core_plugin.get_subnets( ext_subts = self._core_plugin.get_subnets(
context.elevated(), context.elevated(),
filters={'network_id': p['network_id']}) filters={'network_id': [p['network_id']]})
for sub in ext_subts: for sub in ext_subts:
router_subnets.append(sub['id']) router_subnets.append(sub['id'])
else: else: