Red Hat Bugzilla – Bug 16989
kickstart always tries dhcp
Last modified: 2008-05-01 11:37:58 EDT
Since RC2 kickstart always seems to send DHCP requests even when DNS is
configured properly in ks.cfg.
On console 3 I see that reverse lookup works, but then suddenly kickstart
starts searching for a DHCP server, finds it, gets the answer (which says
that there's no configuration for that file), which is displayed on console
4. On console 3 a message is printed that DHCP did not work. As there is
already a working DNS configuration, installation continues (the best sign
is that NFS mount - well, this obviousely means I'm doing a NFS kickstart
insetall - works). However, I don't like our dHCP server being asked by
clients that shouldn't ...
The same config file (just with package list updated) worked fine in RC1.
ks.cfg DNS part:
network --bootproto static --ip 10.0.0.123 --netmask 255.255.255.192
--gateway 10.0.0.190 --nameserver 10.0.0.1
nfs --server myserver.mydomain --dir /my/install/dir
device ethernet 3c59x
Brock please try to reproduce.
reassigning these to firstname.lastname@example.org for further review ...
I can't reproduce this with 7.0 final. Static networking seems to work without
doing a dhcp call.
Tried this with 7.2 RC2. Same problem still - although I do specify static parameters, a DHCP lookup is done. As it fails, anaconda falls back to the
provided static information and works fine.
Can anyone reproduce this?
I did the following:
network --device eth0 --bootproto static --ip 184.108.40.206 --netmask
255.255.255.0 --gateway 220.127.116.11 --nameserver 18.104.22.168
nfs --server p --dir /mnt/test/msw/i386
and no dhcp request was sent.