x
/
group-based-policy
Code Issues Proposed changes

FIP Status active after dissociate. 

The error happens when the FIP is dissociated from the port
and ports get deleted, which are using the VIP port's fixed
IP address as an allowed-address-pairs. The expected behavior
is that dissociation succeeds, and the final status of the
dissociated FIP is “DOWN”. Instead, they are seeing the
dissociation fail with an HTTP 404, and the final FIP status
is “ACTIVE”.
fix here is to catch and ignore "port not found" exceptions.

Change-Id: I7769371b41f390adf668f976fad9ec209b5acf69
This commit is contained in:
Pulkit vajpayee 2022-08-06 10:35:57 +05:30 committed by pulkit vajpayee
parent 549f0f3688
commit 7fe026d9fc
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gbpservice/neutron/plugins/ml2plus/drivers/apic_aim/mechanism_driver.py
View File

@ -4846,7 +4846,10 @@ class ApicMechanismDriver(api_plus.MechanismDriver,
ports_to_notify.extend([x['port_id'] for x in set(notify_pairs)])
for p in sorted(ports_to_notify):
self._notify_port_update(plugin_context, p)
try:
self._notify_port_update(plugin_context, p)
except n_exceptions.PortNotFound:
LOG.info("Port not found %s", p)
def _notify_port_update_bulk(self, plugin_context, port_ids):
# REVISIT: Is a single query for all ports possible?