Red Hat Bugzilla – Bug 622927
F14 Alpha RC2 - /etc/resolv.conf gets corrupted, cannot download packages
Last modified: 2011-03-15 14:25:48 EDT
Created attachment 437985 [details]
Description of problem:
Doing a PXE/kickstart install of F14 Alpha RC2, /etc/resolv.conf get corrupted to only contain:
At which point it cannot download any packages.
Using tail -f it appears that it occurs between these two events:
13:50:59,054 DEBUG anaconda: isys.py:mount()- going to mount /proc/bus/usb on /mnt/sysimage/proc/bus/usb as usbfs with options defaults
13:50:59,189 INFO anaconda: leaving (1) step preinstallconfig
Version-Release number of selected component (if applicable):
Could you also attach your kickstart file?
Created attachment 438069 [details]
Indeed, we are (re)writing out /etc/resolv.conf in preinstallconfig step. What should your correct file look like (what is its content before corrupting in the step)?
Could you also post /tmp/ifcfg.log and /tmp/syslog log files?
Created attachment 438210 [details]
The prior working /etc/resolv.conf contains:
# Generated by NetworkManager
Created attachment 438211 [details]
Thanks for the report.
Only NetworkManager should touch /etc/resolv.conf. Anaconda does it when hostname (not containing any dots) is set in UI or kickstart and socket.getfqdn() finds fqdn for it. It leads e.g. to name servers obtained via DHCP missing in anaconda-generated resolv.conf.
I am going to send a patch.
Fixed in rawhide, will go to anaconda-15.0-1. I want to propose it for F14.
This should be fixed in anaconda-14.17-1 (F14 Beta).
How soon we will have images built with this that I can test? Thanks.
Discussed at today's blocker bug review meeting. We decided not to worry too much about categorizing this as it should be fixed soon anyway, so we will accept it in the expectation it will be closed soon.
orion, the fix for this should be in TC1: can you please test and confirm?
Yup, fixed there.