yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

What you get through the API is just a reflection of DB state, in which a port has IP address regardless of subnet settings.
I don't think output should be affected by the state of the backend.

So IMO, we don't need to fix this.

** Changed in: neutron
       Status: New => Opinion

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

Title:
  Fixed ip info shown for port even when dhcp is disabled

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  As a user it is very confusing (especially in Horizon dashboard)
  having the IP address displayed even when the DHCP is disabled for the
  subnet the port belongs to: the user would expect that the IP address
  shown is actually assigned to the instance, but this is not the case,
  since the DHCP is disabled.

  I asked in the ML about this issue
  (http://lists.openstack.org/pipermail/openstack-
  dev/2014-December/053069.html) and I understood that neutron needs to
  reserve an IP address for a port even in the case it is not assigned,
  anyway I think this info should not be displayed or should be
  differently specified.

  In a first moment I thought about raising the bug against Horizon, but
  I feel the correct place to fix this is in neutron. Before to assign
  this bug to myself I would like to get some feedback by other
  developers, my idea for a possible solution is to add a boolean
  element "assigned" to "fixed_ip" dict with value False when in the
  subnet identified by "subnet_id"  DHCP is disabled.

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