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:

When using the kickstart, it fails to get an IP address via DHCP.  Only errors I get are as follows:

device state change: 7 > 9 (reason 5)
Marking connection 'System eth0' invalid.
Activation (eth0) failed

This is happening for all of our Dell T3500's with the Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet.  If we stick a different NIC in, it works just fine.  Also, there are no problems with the RHEL5 kickstart or any other bootable linux distro we tried.

Finally, if we configure the network statically from the kickstart, it works just fine.  Also, once RHEL6 is installed, dhcp works, so the problem is isolated to the kickstart.

Version-Release number of selected component (if applicable):
RHEL 6.0

Steps to Reproduce:
1. Start a rhel6 kickstart
2.Let NetworkManager try to get an IP address via DHCP
  
Actual results:
dhcp fails and timeouts

Expected results:
dhcp gets an IP address.

Other things:
The kickstart file is on a remote server, so the only configuration we are feeding the kickstart are the boot options, which are as follows:

ks=<url to kickstart file here> initrd=initrd.img xdriver=vesa nomodeset

Is IPv6 enabled on your network?  Are you setting any IP-related options in the kickstart file?  Any chance you can provide more of the logs there so we can see if this is indeed a DHCPv4 timeout or something else?

If this is a DHCP4 timeout, then it's pretty clearly a kernel driver bug as the card isn't handling packets correctly;  in that case we'd need to get some wireshark traces to find out if the DHCP requests are going out correctly, and that the server is correctly returning a response.

Also, what's the PCI VID/PID of the ethernet card?

Since RHEL 6.1 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.

Since RHEL 6.2 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.

Please reopen if you can provide the data requested in comment 2.