Comment 10 for bug 1586931

Reviewed: https://review.openstack.org/338200
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d39d45ab4b9e7f8974e6018ad40def0d79a9909f
Submitter: Jenkins
Branch: stable/liberty

commit d39d45ab4b9e7f8974e6018ad40def0d79a9909f
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:
     neutron/notifiers/nova.py
     neutron/tests/unit/notifiers/test_nova.py

    Closes-bug: #1586931
    Change-Id: Ic72313ad1f787b3cb528e806c843f1fd01eb12f2
    (cherry picked from commit 6e275e38575981386508718bf31e6f88b5a0887d)