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
This commit is contained in:
parent
5d607a13ba
commit
018ed70d23
|
@ -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:
|
||||
|
|
Loading…
Reference in New Issue