group-based-policy/gbpservice/neutron
Pulkit vajpayee a18a79ec30 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
(cherry picked from commit 7fe026d9fc)
2022-08-16 04:00:59 +00:00
..
db Python2/3 compatibility fixes 2022-02-18 17:07:18 +00:00
extensions Python2/3 compatibility fixes 2022-02-18 17:07:18 +00:00
plugins FIP Status active after dissociate. 2022-08-16 04:00:59 +00:00
services Python2/3 compatibility fixes 2022-02-18 17:07:18 +00:00
tests Populate network mtu for erspan 2022-04-27 15:58:16 +00:00
__init__.py Renaming gbp package to gbpservice 2014-12-31 19:13:19 -08:00