[Bug 1013843] Re: resolv.conf empty when doing PXE installations

Launchpad Bug Tracker 1013843 at bugs.launchpad.net
Wed Jul 4 02:50:18 UTC 2012


This bug was fixed in the package casper - 1.319

---------------
casper (1.319) quantal; urgency=low

  * Remove conf.d/compcache as compcache doesn't exist anymore.
    A possible replacement would be zram.
  * Add md4 and des_generic to the initramfs, required by cifs.
  * Revert my previous change as the network-manager override isn't actually
    needed when the /e/n/i logic works (and marks the interface as manual).
  * Update paths to net-$INTERFACE.conf to /run/ as it now lives there instead
    of /tmp. (LP: #1013843)
 -- Stephane Graber <stgraber at ubuntu.com>   Tue, 03 Jul 2012 22:36:16 -0400

** Changed in: casper (Ubuntu Quantal)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to casper in Ubuntu.
https://bugs.launchpad.net/bugs/1013843

Title:
  resolv.conf empty when doing PXE installations

Status in “casper” package in Ubuntu:
  Fix Released
Status in “resolvconf” package in Ubuntu:
  Invalid
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “casper” source package in Quantal:
  Fix Released
Status in “resolvconf” source package in Quantal:
  Invalid
Status in “ubiquity” source package in Quantal:
  Invalid

Bug description:
  Quantal daily image as of 20110615.
  resolvconf 1.65ubuntu4.

  In our environment we do network installs via PXE booting. We noticed
  that name resolution wasn't working during the late_command phase
  (e.g. any apt-get install operations in the ubiquity/late_command
  fail).

  PXE passes IP information (including DNS) to the kernel, and in this
  case, the entry in /etc/network/interfaces is:

  auto eth0
  iface eth0 inet manual

  What we found is that, with this configuration, /etc/resolv.conf will
  be unconfigured (even though DHCP *did* send DNS information):

  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  if I change the /etc/network/interfaces entry  to

  auto eth0
  iface eth0 inet dhcp

  then I run:

  sudo ifup --force eth0

  then /etc/resolv.conf is populated correctly and DNS resolution starts
  working.

  This would be a regression from Precise, where the resolv.conf file
  gets correctly populated even if the interface is set as manual.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1013843/+subscriptions




More information about the foundations-bugs mailing list