Browse Source

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
(cherry picked from commit e7d126f9bc)
(cherry picked from commit 06cbfe0e1d)
(cherry picked from commit 16befa0385)
changes/99/771599/2
Thomas Bachman 7 months ago
parent
commit
1b8f449e25
  1. 2
      neutron/db/l3_db.py

2
neutron/db/l3_db.py

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

Loading…
Cancel
Save