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
..
drivers	FIP Status active after dissociate.	2022-08-16 04:00:59 +00:00
extension_overrides	For queens sync	2018-09-07 16:24:08 -07:00
__init__.py	Extend ML2 core plugin	2016-07-11 21:32:38 -04:00
driver_api.py	Cleanup Queens (part 2)	2020-06-10 13:45:36 -04:00
driver_context.py	Security Group support	2017-10-05 12:14:39 -07:00
managers.py	Cleanup Queens	2020-04-30 17:44:38 -04:00
patch_neutron.py	Cleanup Queens	2020-04-30 17:44:38 -04:00
plugin.py	Merge "Fix session handling" into stable/queens	2021-01-26 03:40:03 +00:00