If we try to delete a VM and to delete the floating IP
associated with the VM at the same time, depending
on the order according to which these requests are processed
Neutron might fail in the deletion of the floating IP,
raising a PortNotFound error. This happens because Neutron
notifies Nova of the network change event and it tries to get
the port to which the FIP is associated. If the port is not there,
Neutron shouldn't raise, it shouldn't send any notification.
Reviewed: https:/ /review. openstack. org/338184 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=9e403b18f03 362872571c1b595 df9567a7c39e29
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 9e403b18f033628 72571c1b595df95 67a7c39e29
Author: rossella <email address hidden>
Date: Sat Jul 2 18:15:32 2016 +0000
When deleting floating IP catch PortNotFound
If we try to delete a VM and to delete the floating IP
associated with the VM at the same time, depending
on the order according to which these requests are processed
Neutron might fail in the deletion of the floating IP,
raising a PortNotFound error. This happens because Neutron
notifies Nova of the network change event and it tries to get
the port to which the FIP is associated. If the port is not there,
Neutron shouldn't raise, it shouldn't send any notification.
Conflicts: notifiers/ nova.py tests/unit/ notifiers/ test_nova. py
neutron/
neutron/
Closes-bug: #1586931 3cb528e806c843f 1fd01eb12f2 86508718bf31e6f 88b5a0887d)
Change-Id: Ic72313ad1f787b
(cherry picked from commit 6e275e385759813