Red Hat Bugzilla – Bug 483257
resolv.conf rewritten even though PEERDNS=no
Last modified: 2014-03-31 13:55:39 EDT
Updated this morning from Rawhide. Rebooted. /etc/resolv.conf was rewritten when my DHCP interface (eth0) was brought up, even though I have PEERDNS=no in /etc/sysconfig/network-scripts/ifcfg-eth0.
This really should have been an alpha blocker. At the very least, it should be a beta blocker. The problem is that the source_config function in /etc/sysconfig/network-scripts/network-functions is buggy -- it assumes that the config file name isn't an absolute path. I will attach a patch which fixes this as well as does a number of other related clean-ups.
Created attachment 331078 [details]
patch to /etc/sysconfig/network-scripts/network-functions
Hello? Anybody there? I filed this ticket over a month ago and even provided a patch, and yet nobody has done anything with it. Surely breaking /etc/resolv.conf is a release blocker?
1) got busy with other things
2) it's not necessarily correct in that config files in random locations isn't really supposed to work. It could be easily fixed in dhclient-script too
3) it leads to the question of whether the PARENTCONFIG stuff there really is still needed
Concerning (2), while my fix catered to the fact that there was all that weird code in the script to allow config files in random locations, that's not the bug I initially reported or fixed. The bug is that even when the config files are all in the standard locations, dhclient changes resolv.conf even when PEERDNS is no. This is surely a release blocker.
Sure, but while I'm looking at it, I'd like to get the whole thing right.
Will be in 8.91-1.