yahoo-eng-team team mailing list archive

[Gabriel Hurley <1171823@xxxxxxxxxxxxxxxxxx>]

As reported in the comments, this is a bug in quantum propagated through
the nova API. Horizon is just displaying the information it receives.

** Changed in: horizon
       Status: New => Invalid

** Changed in: horizon
     Assignee: (unassigned) => Gabriel Hurley (gabriel-hurley)

-- 
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/1171823

Title:
  Display of the floating ip is broken when using overlapping IP
  addresses

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  Release: 2013.1 (Grizzly)

  I have a single node grizzly installation with Quantum and I have
  enabled overlapping IP addresses. I do the following to encounter the
  issue:

  1. Create two networks net1 and net2 with in the same tenant, both having same subnet but each network has its own router. The subnet used is 192.168.2.0/24.
  2. I launch a VM, VM1 on net1. It gets the IP 192.168.2.2 as expected.
  3. I then associate a floating IP, 10.5.12.23 to this VM. The Horizon instances page displays both IPs for VM1 correctly as expected.
  4. Now I launch another VM, VM2 on net2. 
  5. VM gets the IP 192.168.2.2 as expected. 
  6. And I have not associated any floating IP to VM2.
  7. But Horizon instances page display the floating IP associated with VM1 against VM2 as well! Refer to the attached screenshot.

  VM2 should not be displaying the floating IP associated to another VM
  on another network.

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