Bugzilla – Bug 96662
network dialog has garbage in domain search1/2/3 fields
Last modified: 2008-07-16 15:47:54 UTC
during a vnc installation, changing the hostname/domainname in yast network config dialog is not possible anymore. search domain 1 contains 'suse.de' search domain 2 contains 'ver' search domain 3 contains '10.10.2.88'
Created attachment 42174 [details] bug96662.tar.bz2 resolv.conf contains already garbage, the eth0.info file looks ok to me. probably more a dhcpcd or sysconfig bug.
The host and domain name problem may be a duplicate of bug 63423 which is fixed in yast2-network-2.12.2. Indeed there is garbage in resolv.conf already. Reassigning to modify_resolvconf.
this is still not fixed
Is this a bug in modify_resolvconf at all? As dhcpcd-eth0.info does not contain anything special I doubt that modify_resolvconf was called with funny data or behaved strangely. y2log shows: YaST2/y2log-2005-07-14 20:09:15 <1> cube(5600) [YCP] NetworkConfig.ycp:86 Writing configuration YaST2/y2log-2005-07-14 20:09:15 <1> cube(5600) [YCP] DNS.ycp:170 Writing configuration YaST2/y2log-2005-07-14 20:09:15 <1> cube(5600) [YCP] DNS.ycp:176 nameservers=["10.10.2.88", "10.10.0.1", "149.44.160.146"] YaST2/y2log:2005-07-14 20:09:15 <1> cube(5600) [YCP] DNS.ycp:177 searchlist=["suse.de", "ver", "10.10.2.88"] YaST2/y2log-2005-07-14 20:09:15 <1> cube(5600) [YCP] DNS.ycp:178 hostname=linux YaST2/y2log-2005-07-14 20:09:15 <1> cube(5600) [YCP] DNS.ycp:179 domain=site YaST2/y2log-2005-07-14 20:09:15 <1> linux(5600) [YCP] network/runtime.ycp:35 Running SuSEconfig ... Is yast2 modifying resolv.conf directly?
If modify_resolvconf writes this search lines, then it was most probably told to do so. So if you think modify_resolvconf is involved at all, then please tell me where and when and how it was called.
search suse.de ver 10.10.2.88 nameserver 10.10.2.88 nameserver 10.10.0.1 nameserver 149.44.160.146 cube:~ # cat /etc/SuSE-release SUSE LINUX 10.0 (PPC) beta2 VERSION = 10.0 cube:~ # cat /var/lib/dhcpcd/dhcpcd-eth0.info IPADDR=10.10.1.180 NETMASK=255.255.0.0 NETWORK=10.10.0.0 BROADCAST=10.10.255.255 GATEWAY=10.10.0.8 HOSTNAME='cube' DOMAIN='suse.de' NISDOMAIN='suse.de' DNS=10.10.2.88,10.10.0.1,149.44.160.146 NTPSERVERS=149.44.160.50,149.44.160.54,149.44.160.1 NISSERVERS=149.44.160.146,149.44.160.50,10.10.0.1 LPRSERVERS=149.44.160.33 LOGSERVERS=10.10.125.16 DHCPSID=10.10.125.16 DHCPGIADDR=0.0.0.0 DHCPSIADDR=10.10.125.16 DHCPCHADDR=00:02:55:6F:97:29 DHCPSHADDR=00:09:6B:76:04:92 DHCPSNAME='boettger.suse.de' LEASETIME=5184000 RENEWALTIME=2592000 REBINDTIME=4536000 INTERFACE='eth0' CLASSID='Linux 2.6.13-rc6-git13-20050822220010-ppc64 ppc' CLIENTID=00:02:55:6F:97:29 I dont see it on mac.suse.de for some reason.
Do I understand correctly that the problem shows up only during installation, and not in the installed system?
it happens of course also in the installed system. yast is not involved anymore after 2 or 3 reboots.
Can you please set DHCLIENT_DEBUG=yes in /etc/sysconfig/network/dhcp so the modify_resolvconf arguments are logged? thanks
likely an off-by-one error in one of the apps that modifies resolv.conf. doesnt happen if the backup file is empty
where is the source code for the applications that touch /etc/resolv.conf? Guess I have to fix that one myself.
how does one get from a to b, what options are passed to modify_resolv.conf? ==> resolv.conf <== search suse.de ver 10.10.2.88 nameserver 10.10.2.88 nameserver 10.10.0.1 nameserver 149.44.160.146 ==> resolv.conf.saved.by.dhcpcd.eth0 <== domain suse.de nameserver 10.10.2.88
See comment #9!
it is already broken, script cant do anything about it. checkerberry:~/x # head -n 33 /dev/shm/modify_resolvconf.1932.txt modify -s dhcpcd -p dhcpcd -i 1924 -l suse.de ver 10.10.2.88 -n 10.10.2.88 10.10.0.1 149.44.160.146 -f /sbin/modify_resolvconf -e eth0 -t If you don't like dhcpcd to change your nameserver settings then either set DHCLIENT_MODIFY_RESOLV_CONF=no in /etc/sysconfig/network/dhcp, or set MODIFY_RESOLV_CONF_DYNAMICALLY=no in /etc/sysconfig/network/config or (manually) use dhcpcd with -R. If you only want to keep your searchlist, set DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or (manually) use the -K option. 'modify' '-s' 'dhcpcd' '-p' 'dhcpcd' '-i' '1924' '-l' 'suse.de ver 10.10.2.88' '-n' '10.10.2.88 10.10.0.1 149.44.160.146 ' '-f' '/sbin/modify_resolvconf' '-e' 'eth0' '-t' 'If you don't like dhcpcd to change your nameserver settings then either set DHCLIENT_MODIFY_RESOLV_CONF=no in /etc/sysconfig/network/dhcp, or set MODIFY_RESOLV_CONF_DYNAMICALLY=no in /etc/sysconfig/network/config or (manually) use dhcpcd with -R. If you only want to keep your searchlist, set DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or (manually) use
checkerberry:~/x # env -i grep -r suse.de /var/lib/dhcpcd/ /var/lib/dhcpcd/dhcpcd-eth0.info:DOMAIN='suse.de' /var/lib/dhcpcd/dhcpcd-eth0.info:NISDOMAIN='suse.de' /var/lib/dhcpcd/dhcpcd-eth0.info:DHCPSNAME='boettger.suse.de' /var/lib/dhcpcd/dhcpcd-eth0.info.old:DOMAIN='suse.de' /var/lib/dhcpcd/dhcpcd-eth0.info.old:NISDOMAIN='suse.de' /var/lib/dhcpcd/dhcpcd-eth0.info.old:DHCPSNAME='boettger.suse.de'
Is DHCLIENT_KEEP_SEARCHLIST in /etc/sysconfig/network/dhcp set to yes?
yes, thats likely the default.
found the bug, there is no 'search' line in the old resolv.conf, only domain, and with the new default KEEP_SEARCHLIST the bug shows up. I'll fix it on Monday.
It should be fixed with /work/built/mbuild/aust-poeml-1219. Can you confirm that?
The bug didn't show during 10.0 beta so far but it is relevant there as well. I submitted a fixed package, so in 10.0 and STABLE it should be fixed.
just do a vnc installation, or ssh