Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.