yahoo-eng-team team mailing list archive

[Gary Kotton <1182894@xxxxxxxxxxxxxxxxxx>]

Hi,
This is by design. If you wish to create a port without and IP address then you should not create a subnet and just allocate a port on the network.
Thanks
Gary

** Changed in: quantum
       Status: In Progress => Invalid

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

Title:
  Don't allocate an IP in subnets with disable_dhcp set to True

Status in OpenStack Quantum (virtual network service):
  Invalid

Bug description:
  Way to reproduce:

  1- Create a network and a subnet with disable-dhcp set to True.

       $ quantum net-create net1
       $ quantum subnet-create net1 10.0.0.0/24 --disable-dhcp

  2- Now boot a new VM in the previous network:

      $ nova boot --flavor ... --nic net-id=<our net1> ...

  3- Now execute:

      $ nova list

  You will see that the VM have an IP allocated to it, else the VM will
  never get this IP because the subnet created doesn't have a DHCP
  server (dnsmasq not running), so it's wrong.

  The behavior that i was expecting is that nova list will not show an
  IP because there is None.

  This behavior is more annoying when you have a public network, usually
  i created my public netword with disable-dhcp option, but because when
  i try to boot a VM without specifying any network it will get all of
  the tenant networks, even the public one, and than "nova list" will
  show that an IP was allocated from the public network, which certainly
  not how ip should be allocated from a public network.

  I hope that i understood this correctly, because this behavior was
  very confusing for me.

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