Hide Forgot
Description of problem: I see the exact same problem as: https://bugzilla.redhat.com/show_bug.cgi?id=260621 The work-around outlined there works as well. If the kickstart has network --bootproto=dhcp, the network prompt comes up as in the linked bug. ip=dhcp works for that. If the kickstart has a static configuration, anaconda tries to configure it with DHCP. Version-Release number of selected component (if applicable): 13.21.117 How reproducible: 100% Steps to Reproduce: 1.Create initrd with ks file ( or use multiple initrds if your boot loader supports it), so it will be available as ks=file://... 2.use a kickstart that has url --url ( nfs works ) I didn't have the time to test with the kickstart from http as well. I will do that if i have the time. Actual results: Anaconda becomes interactive. Expected results: Installation should complete Additional info:
There are two parts to network bringup. First, we need to know how to get the kickstart file. This is accomplished via checking the command line options or prompting the user. Second, we apply the kickstart's networking options. This could also potentially prompt the user. Please attach your kickstart file (minus any passwords, etc.) and /tmp/anaconda.log and /tmp/syslog to this bug report. Thanks.
I don't have the files at hand right now, and it can take a while until i have the time to reproduce this. My ks file is in the initrd, so there is no networking required to get it.
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.