[Bug 1013843] Re: resolv.conf empty when doing PXE installations
Stéphane Graber
stgraber at stgraber.org
Fri Jun 22 13:50:58 UTC 2012
It sounds pretty unlikely to be a bug in resolvconf itself, so marking
it invalid against resolvconf for now.
The excepted behaviour on netboot is:
- No network manager
- No ifupdown
- Configured /etc/resolv.conf
I'll have to do some more tests but the changes I pushed early in the
quantal cycles were used to deploy a few hundred machines using
netboot+cifs, so it at least to some extent worked in the past...
** Changed in: resolvconf (Ubuntu Quantal)
Status: New => Invalid
--
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:
Invalid
Status in “ubiquity” package in Ubuntu:
Invalid
Status in “casper” source package in Quantal:
New
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