Description of problem: There does not seem to be any way of extending the DHCP timeout to more than 45 seconds. This prevents installation via PXE. Even if the dhclient timeout is extended, NetworkManager will kill it before the address is obtained. This is (as always) a problem with a Cisco switch which takes 60 seconds to start forwarding traffic. I believe this is related to the etherchannel bonding rather than portfast but either way, altering the switch config is not permitted. DHCP would work perfectly well if the timeout could be extended. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Could be reproduced by turning off the DHCP server at the right time and then turning it back on 60 seconds later. 2. 3. Actual results: The message "There was an error configuring your network interface." is shown and using the retry button only produces the same results. Expected results: Some combination of nicdelay and dhcptimeout would allow the DHCP timeout to be set to 120 seconds. Even better, keep DHCP running in the background rather than giving up and don't keep taking the interface up and down. Or, in the config dialog, allow the timout to be altered. Additional info: This might be relevant http://old.nabble.com/DHCP-timeout-is-too-short-for-this-college-network-td27105772.html
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.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0832.html