From 018ed70d23ec5f8bd0667e404c40ad4b60bd91b6 Mon Sep 17 00:00:00 2001 From: Boden R Date: Thu, 18 Apr 2019 15:26:11 -0600 Subject: [PATCH] use publish for SUBNETPOOL_ADDRESS_SCOPE callback events Today all the code for SUBNETPOOL_ADDRESS_SCOPE callback events uses the payload style kwargs, however 1 use still calls notify() rather than publish() which should be used for the payload style callbacks. This patch fixes the issue. NeutronLibImpact Change-Id: Icc598169cc07db7270d452834439953b3bf273c2 --- neutron/db/db_base_plugin_v2.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/neutron/db/db_base_plugin_v2.py b/neutron/db/db_base_plugin_v2.py index 16f6509c44b..89be2dc963c 100644 --- a/neutron/db/db_base_plugin_v2.py +++ b/neutron/db/db_base_plugin_v2.py @@ -1276,11 +1276,11 @@ class NeutronDbPluginV2(db_base_plugin_common.DbBasePluginCommon, if subnetpool.address_scope_id: # Notify all affected routers of any address scope changes - registry.notify(resources.SUBNETPOOL_ADDRESS_SCOPE, - events.AFTER_UPDATE, - self.onboard_network_subnets, - payload=events.DBEventPayload( - context, resource_id=subnetpool_id)) + registry.publish(resources.SUBNETPOOL_ADDRESS_SCOPE, + events.AFTER_UPDATE, + self.onboard_network_subnets, + payload=events.DBEventPayload( + context, resource_id=subnetpool_id)) onboard_info = [] for subnet in subnets_to_onboard: