yahoo-eng-team team mailing list archive

[Édouard Thuleau <edouard.thuleau@xxxxxxxxxxxxx>]

The bug is not concern Horizon.
It is related to Nova https://bugs.launchpad.net/nova/+bug/1168994

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

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

Title:
  Overlapping IP error with floating IPs

Status in OpenStack Dashboard (Horizon):
  Invalid

Bug description:
  When Quantum allow to use overlapping IP, Horizon fails to list
  correctly floating IPs associated to a port with a private IP value
  use on multiple ports.

  For exemple, we have 2 networks with a same value for their subnet:
  - network 'net1' with subnet 'subnet1' 10.0.0.0/24
  - network 'net2' with subnet 'subnet2' 10.0.0.0/24

  Start an instance 'VM1' and plug it on the network 'net1' with IP '10.0.0.3'.
  Associate a floating IP to that private IP '30.0.0.3'. All work fine.

  Now, start another instance 'VM2' and plug it on the network 'net2'
  with IP '10.0.0.3' (same IP than 'VM1' but on another network). 'VM2'
  starts correctly but Horizon list it with a associated floating IP
  '30.0.0.3' when no floating IP is associated on that port.

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