yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

Isn't that the design point, if you've configured to use dhcp in your
cloud that should be how networks are configured.

Marking as Opinion, please move back if you think there is a bug here.

** Summary changed:

- can not get network info from metadata server
+ can not get network info from metadata server when cloud is set to use dhcp

** Changed in: nova
       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/1352105

Title:
  can not get network info from metadata server when cloud is set to use
  dhcp

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  I want to use cloudinit to get the network info and write it into the network configuration file,
  but it failed because cloudinit didn't get the network info.
  In the vm, I used curl to test the metadata as below
  #curl http://169.254.169.254/openstack/latest/meta_data.json
  the reponse info didn't contain network info.
  See following code in nova/virt/netutils.py
          if subnet_v4:
              if subnet_v4.get_meta('dhcp_server') is not None:
                  continue
  It seems that when vm use  neutron dhcp, network info will be ignored in meta_data.json

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