yahoo-eng-team team mailing list archive

[Steve McLellan <1413755@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Repro (in stock devstack):
1) Create an instance on a private network
2) Create and associate a floating IP
3) Create and try to associate a second IP

The second time will cause an error "Error: The requested instance port
is already associated with another floating IP."

Note that the instance's port is listed both times, though it's not
possible to attach two FIPs to the same fixed IP. It looks like there is
some filtering code in api/neutron.py but it may not be doing the right
thing.

** Affects: horizon
     Importance: Undecided
     Assignee: Steve McLellan (sjmc7)
         Status: New

** Changed in: horizon
     Assignee: (unassigned) => Steve McLellan (sjmc7)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1413755

Title:
  Associate FIP: ports appearing when already assigned floating IPs

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Repro (in stock devstack):
  1) Create an instance on a private network
  2) Create and associate a floating IP
  3) Create and try to associate a second IP

  The second time will cause an error "Error: The requested instance
  port is already associated with another floating IP."

  Note that the instance's port is listed both times, though it's not
  possible to attach two FIPs to the same fixed IP. It looks like there
  is some filtering code in api/neutron.py but it may not be doing the
  right thing.

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