The Neutron API is only associating a floating IP with an internal port [0], there is no check for a server as that is under the purview of Nova.
Neutron will only raise a 409 on a 'create' call if the floating IP is already in-use, but not on a call to update it - either clearing or moving to another port.
I am curious to see what the Nova team thinks as it as according to their API the server add floating IP code has been deprecated [1].
The Neutron API is only associating a floating IP with an internal port [0], there is no check for a server as that is under the purview of Nova.
Neutron will only raise a 409 on a 'create' call if the floating IP is already in-use, but not on a call to update it - either clearing or moving to another port.
I am curious to see what the Nova team thinks as it as according to their API the server add floating IP code has been deprecated [1].
[0] https:/ /docs.openstack .org/api- ref/network/ v2/index. html#floating- ips-floatingips /docs.openstack .org/api- ref/compute/ #add-associate- floating- ip-addfloatingi p-action- deprecated
[1] https:/