Red Hat Bugzilla – Bug 999106
When performing a kickstart with static ip parameters on a network with no dhcp, anaconda hangs looking for dhcp
Last modified: 2015-02-26 13:46:56 EST
Description of problem:
When attempting to kickstart an installation with RHEL 6.4 on subnets without DHCP servers on them, and the following parameters passed on the kernel line (as well as the static ip information set in the kickstart file) the installation hangs searching for DHCP information and never prompts to put in networking manually:
vmlinuz initrd=initrd.img ip=X.X.X.X netmask=X.X.X.X gateway=X.X.X.X dns=X.X.X.X
The line in the kickstart is specified as:
network --device=eth0 --onboot yes --bootproto=static ip=172.26.6.152 netmask=255.255.255.0 gateway=172.26.6.1 --noipv6
When modifying the line to look like the following there are no issues:
network --device=eth0 --onboot=yes --ip=172.26.6.152 --netmask=255.255.255.0 --gateway=172.26.6.1 --noipv6
So certainly the correct syntax is using the '--' however without them perhaps a timeout could be added for how long DHCP is requested before it times out and prompts for networking parameters to be checked/passed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Eternal hanging waiting for DHCP request to be fulfilled
Eventually Anaconda stops and prompts for networking information to be repopulated manually
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
I don't really see this as a bug - the RHEL6 kickstart documentation clearly says that the correct form of the IP address argument is "--ip". Any other forms, such as "ip", are not supported and can cause undefined behavior, such as the issue you are seeing.