RHEL-4 fails to asign IP

pbdlists at pinboard.com pbdlists at pinboard.com
Thu Mar 10 15:25:16 UTC 2005


I wonder whether I'm the only one having this problem (and thus probably
doing something wrong) of if there really is a problem.

We have a Satellite Server and we've been kickstarting servers from it
for months. No problem. For various tests I probably kickstarted
machines from within vmware well over a hundred times; boot off the
RHEL-iso disk1, type 'linux ks=http://ourserver/path/to/label', wait
for the box to appear to input IP, netmask, gateway and DNS (we have no
DHCP in that network segment and there is no chance there ever will be
one).

The same procedure does not work any more for RHEL-4-WS; the IP settings
entered in the box are not applied. After a timeout I can only continue
with the CD installation. Switching to tty2, there is an eth0, but
without IP. Assigning the IP and routes in that shell works and the
interface is usable. But this is not a workaround, as switching to a
shell can only be done after selecting to continue with the CD
installation.

- checksum of the ISO image used is fine
- same problem with RHEL-4-WS and RHEL-4-DT (desktop)
- same procedure on the same machine works file for RHEL-3-WS

Unfortunately I don't have a physical machine to see whether the same
thing happens there.

What the heck am I doing wrong?

Kurt




More information about the Kickstart-list mailing list