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

[Stéphane Graber]

The cause of the problem was a change in ipconfig from writing
/tmp/net-$DEVICE.conf to writing /run/net-$DeVICE.conf and breaking
23networking in the process.

I did a few more tests here and fixed some code duplication and missing
kernel modules with cifs but it looks like it's all working now, NM is
running but not touching the interface, resolv.conf contains the
expected content and the interface is properly configured.

-- 
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