← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1926045] Re: Restrictions on FIP binding

 

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

** Changed in: neutron
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1926045

Title:
  Restrictions on FIP binding

Status in neutron:
  Expired

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1926045/+subscriptions



References