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

[Thomas Hood]

*** This bug is a duplicate of bug 388060 ***
    https://bugs.launchpad.net/bugs/388060

@Daniel: What's in /var/log/netboot.config on the affected system at the
point where you can't connect?

We have established that nothing is in /run/network/interface/ then, but
casper should have written /run/network/interface/casper.  It appends
the latter file to /root/var/log/netboot.config.  If we see

    # /etc/resolv.conf
    # Autogenerated by casper
    search canonical.com
    domain canonical.com
    nameserver 10.153.104.60

in there then we can conclude that /run/network/interface/casper got
written but was deleted later.

If /run/network/interface/casper never got written then we need to debug
scripts/casper-bottom/23networking.  We need to find out why the code
quoted in #11 is never reached.

Can you add some logging commands to the script to find out what the
results are of the individual tests?  The tests I have in mind are the
following ones.

    -f /root/etc/resolv.conf 
     -z "$(cat /root/etc/resolv.conf)"
    -n "${DEVICE}"
     -e /tmp/net-"${DEVICE}".conf 
    -x /root/sbin/resolvconf 
    -L /root/etc/resolv.conf

-- 
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:
  New
Status in “resolvconf” package in Ubuntu:
  New
Status in “ubiquity” 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/casper/+bug/1013843/+subscriptions