This is not a bug either in Nova. Please take a look at this Tempest API test:
https://github.com/openstack/tempest/blob/master/tempest/api/compute/floating_ips/test_floating_ips_actions.py#L109 and its failure as a consequence of the proposed Neutron fix: https://github.com/openstack/tempest/blob/master/tempest/api/compute/floating_ips/test_floating_ips_actions.py#L109 ** Changed in: nova 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): Invalid 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
