Restrictions on FIP binding

[conna]

Restrictions on FIP binding

1.associate fip-1 with port-1
openstack floating ip set --port ffc92b69-caf8-4a9d-9b53-c970ce768acd 97238adf-d744-4046-9016-32e32875fa52
2.associate fip-1 with port-2
openstack floating ip set --port 32a28a36-d3e8-440a-b3bd-e7f35144da54 97238adf-d744-4046-9016-32e32875fa52

I use a fip that is already added to a devices to bind，it works.
That is,FIP can be added to other devices when it is already bound.

This feature, in the case of user error, can affect the associated routers and vm

I think FIP binding should have restriction.

[Slawek Kaplonski (slaweq)]

Can You tell us exact steps how to reproduce the issue?

[LIU Yulong (dragon889)]

A floating IP can be UPDATEd to re-bind to a new port, no matter the current binding state. So it is a feature, not a bug.

[Brian Haley (brian-haley)]

Can you give more information on why you re-opened this bug?

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]