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

Thomas Hood 1013843 at bugs.launchpad.net
Mon Jun 18 19:09:56 UTC 2012


Thanks very much for the additional info. The error message "cat:
/run/resolvconf/interface/*: No such file or directory" indicates that
resolvconf has had no nameserver information registered with it. It
seems that nothing has called resolvconf to register the nameserver
information obtain via DHCP.

When you define eth0 as an inet dhcp i'face in /etc/network/interfaces
and do "ifup eth0", ifup starts one of the standard DHCP clients, which
are integrated with resolvconf. That's why name service starts working.

I don't know much about Ubiquity. Someone who does know Ubiquity well
will be better equipped than I am to carry on the investigation with
you.

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

Title:
  resolv.conf empty when doing PXE installations

Status in “resolvconf” package in Ubuntu:
  New

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/resolvconf/+bug/1013843/+subscriptions




More information about the foundations-bugs mailing list