Description of problem:
I have a system setup to install according to options described in my PXE configuration. These include ks=, ip= and netmask= settings. If I only use ks=http://192.168.0.254/workstation.cfg, anaconda gets a dhcp lease and kicks just fine.
If I add ip=192.168.0.254, it says that it can't find the ks server, even though it's on the same subnet (192.168.0.254).
When I add netmask=255.255.255.0, again the kick works fine, but it gets a dhcp lease, ignoring the ip= setting.
Version-Release number of selected component (if applicable):
anaconda-22.214.171.124-1, or whatever is the default with RHEL5.4
Always, at least for me.
Also, I should note that while in anaconda I have used 'cat /proc/cmdline' to verify the existence of the ip= and netmask= options, and have used ifconfig and the logs to verify that I am instead getting a different IP via DHCP.
Are you passing a ksdevice=ethX parameter as well? If not, try that.
Yes. The complete list of options being passed are:
ksdevice=eth0 load_ramdisk=1 initrd=initrd.img network ks=http://192.168.0.254/workstation.cfg noipv6 ip=192.168.0.5 netmask=255.255.255.0
Note that the .254 ip= value I mentioned in my initial report was a typo
Can you pass loglevel=debug and start up the installer and get to the graphical part, then go to tty2 and collect the contents of /tmp and attach it to this bug.
Created attachment 361690 [details]
contents of /tmp during install
Tried setting everything up from scratch again. Same behavior as before: ip= seems to be being ignored. I set loglevel=debug and am attaching a tarball of /tmp. I excluded the header files, as they took up a lot of space and I'm assuming they're not relevant. I also created a /tmp/anaconda_info/ with the contents of /proc/cmdline and the output of ifconfig.
Looking at /tmp/anaconda.log, loader does set up eth0 with the static IP but when it tries to fetch the kickstart file, that fails. So it goes back and tries dhcp on eth0. DHCP succeeds and the system uses 192.168.0.20.
I don't know the details of your LAN configuration. Can you try passing the gateway= parameter as well as the ip= and netmask= parameter? Based on the DHCP lease you received, your gateway is also 192.168.0.254.
No additional info provided, cannot reproduce on my VMs.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.