Bug 278551

Summary:	dhcpcd doesn't write "search"
Product:	[openSUSE] openSUSE 10.3	Reporter:	Michal Zugec <mzugec>
Component:	Network	Assignee:	Peter Varkoly <varkoly>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Alpha 4plus
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michal Zugec 2007-05-28 06:47:38 UTC

openSUSE 10.3 Alpha4
dhcpcd-1.3.22p14-259
/etc/sysconfig/network/dhcp.DHCLIENT_MODIFY_RESOLV_CONF=yes
/etc/sysconfig/network/config.MODIFY_RESOLV_CONF_DYNAMICALLY=yes

/etc/resolv.conf is written without "search" option, but /var/lib/dhcpcd/dhcpcd-eth0.info contains this information

This worked fine with dhcpcd-1.3.22pl4-247

Peter, if you need any logs, just ask me - I can give you also ssh access to that machine

Comment 1 Peter Poeml 2007-05-29 10:58:34 UTC

Reassigning to the other Peter

Comment 2 Peter Varkoly 2007-05-30 11:41:54 UTC

please give me ssh access to that machine

Comment 6 Peter Varkoly 2007-05-30 16:05:45 UTC

there is no configuration for eth1

Comment 7 Michal Zugec 2007-06-01 15:40:47 UTC

It was probably broken later (after installation file was there)

Now the same situation:
- configuration is created for eth1
- dhcp is used
- in sysconfig network-config/dhcp is dhcpcd configured to replace resolv.conf
- in resolv. conf there is no information about "search"
This is important:
during rcnetwork start I can see this error/warning:
Error while executing:
   Command 'ip route replace to 10.20.0.1169.254.0.0/16 dev eth1' returned:
  Error: an inet prefix is expected rather than "10.20.0.1169.254.0.0/16".
   Configuration line: 10.20.0.1169.254.0.0 - 255.255.0.0 eth1


IP address obtained from dhcp is 10.20.4.1/21

Comment 8 Peter Varkoly 2007-06-06 09:30:35 UTC

I think it depends on the netmask 255.255.248.0.
I can not reproduce this problem in our network.
I'm going to setup a test network.

Comment 9 Peter Varkoly 2007-06-07 10:12:57 UTC

It is definitely not a bug of dhcpcd. 
I've tested a lot of times, dhcpcd detects the DHCP  statements domain and searchlist correct and calls modify_resolvconf with the correct attributes:

dhcpcd[2697]: dhcpConfig: modify_resolvconf args: modify -s dhcpcd -p dhcpcd -i \
  2697 -l suse.cz suse.de -n 10.20.0.2 10.20.0.8  -f /sbin/modify_resolvconf -e \
  eth1 -t "..."

It can be seen it in /var/log/boot.msg. Calling modify_resolvconf manually with this parametes the /etc/resolv.conf is OK but the /etc/resolv.conf after booting do not contains the search list.

I've modified /sbin/modify_resolvconf to be more verbose.

My problem is, that I can not reproduce this problem on other workstation.

1. How long can I use your workstation?
2. Can you test this problem on an other workstation?

Comment 10 Michal Zugec 2007-06-07 10:34:28 UTC

added Christian Zoz (sysconfig->modify_resolvconf maintainer) into CC

Comment 11 Michal Zugec 2007-06-07 10:55:57 UTC

1 : until Monday. after that you'll need to ping me to boot into that system again
(but I would like this bug/problem will be solved, so if that's not enought )

2 : I'm afraid not. Except that machine I have only my laptop, but unfortunately I don't have time for installing any Alpha there (without access to my work)

Is it possible that resolv.conf is just copy from 1.st stage of installation?
I'm using my own inst-sys - that will be in next release

Comment 12 Peter Varkoly 2007-06-10 10:21:01 UTC

removing all resolv.conf* in /etc and restarting the computer now it works fine.