This is not a bug, this is the expected behavior of the floating ip API in Neutron. Please look at this Tempest test case failure that was triggered by the proposed fix (https://review.openstack.org/#/c/425563/):
http://logs.openstack.org/63/425563/1/check/gate-tempest-dsvm-neutron- linuxbridge-ubuntu- xenial/4601f1d/console.html#_2017-01-26_08_51_05_811634 The source of this test is the following: https://github.com/openstack/tempest/blob/master/tempest/api/network/test_floating_ips.py#L65 We are clearly saying in this test case's code that we allow to change a floating ip association without disassociating if before ** Changed in: neutron Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1659215 Title: Should not allow assign floating IPs that are already assigned to another port Status in neutron: Invalid Status in OpenStack Compute (nova): In Progress Bug description: While associate floating ip to instance, we did not check the floating IP is already assigned to another port or not: http://git.openstack.org/cgit/openstack/nova/tree/nova/network/neutronv2/api.py#n1684 It is understandable to allow re-assign to the same port, but we should not re-assgin if it is already assigned to other ports. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1659215/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
