yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Triaged => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1298002

Title:
  Nova does not inject DHCP config to guest OS

Status in OpenStack Compute (nova):
  Expired

Bug description:
  When booting servers using Nova configured for injecting network setup
  into the guest OS, Nova is not injecting DHCP network configurations.

  Nova.conf has these set:
  # Whether to attempt to inject network setup into guest
  # (boolean value)
  flat_injected=true

  # Template file for injected network (string value)
  injected_network_template=$pybasedir/nova/virt/interfaces.template

  When you boot a server with a DHCP network, the network configuration is not included on the config drive at /openstack/content/0000.
  The network configuration does get transmitted if you boot with a static fixed IP like this:
  nova --image myimage --flavor 2 myVM --config-drive=true --nic net-id=a6222a6b-d3f5-4cdd-8afd-6c7b29d65906,v4-fixed-ip=192.168.0.10

  This prevents you from being able to capture a snapshot of a VM that
  is configured with a static IP address and deploy/boot the snapshot
  image using a DHCP configured network.  The resulting VM will still
  come up on the capture source's static IP.

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