From 7efe183d04c067310174b4d828c4e3f69612a5af Mon Sep 17 00:00:00 2001 From: Adit Sarfaty Date: Wed, 15 Aug 2018 10:18:01 +0300 Subject: [PATCH] NSX|V3 update port binding for callbacks notifications When updating a port, the original port used in notifications should have the port binding fields, or else some services (like FWaaS) might fail. Change-Id: I3a0d66b2741504903c9df92fcdd8520765d73f9d --- vmware_nsx/plugins/nsx_v3/plugin.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/vmware_nsx/plugins/nsx_v3/plugin.py b/vmware_nsx/plugins/nsx_v3/plugin.py index d9c9ca566a..d1261ebc47 100644 --- a/vmware_nsx/plugins/nsx_v3/plugin.py +++ b/vmware_nsx/plugins/nsx_v3/plugin.py @@ -3394,7 +3394,10 @@ class NsxV3Plugin(agentschedulers_db.AZDhcpAgentSchedulerDbMixin, break with db_api.context_manager.writer.using(context): + # get the original port, and keep it honest as it is later used + # for notifications original_port = super(NsxV3Plugin, self).get_port(context, id) + self._extend_get_port_dict_qos_and_binding(context, original_port) self._remove_provider_security_groups_from_list(original_port) port_data = port['port'] nsx_lswitch_id, nsx_lport_id = nsx_db.get_nsx_switch_and_port_id(