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.
Bug 663820 - Unable to extend DHCP timeout
Summary: Unable to extend DHCP timeout
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 669019 744956 756082 769145
TreeView+ depends on / blocked
 
Reported: 2010-12-16 23:02 UTC by John Newbigin
Modified: 2018-11-28 21:34 UTC (History)
7 users (show)

Fixed In Version: NetworkManager-0.8.1-22.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 769145 (view as bug list)
Environment:
Last Closed: 2012-06-20 13:41:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Backport of the previous patch for RHEL-6.3 (5.93 KB, patch)
2012-03-02 12:54 UTC, Jirka Klimes
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Legacy) 64543 0 None None None Never
Red Hat Product Errata RHBA-2012:0832 0 normal SHIPPED_LIVE NetworkManager bug fix and enhancement update 2012-06-19 20:49:16 UTC

Description John Newbigin 2010-12-16 23:02:15 UTC
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

Comment 2 RHEL Program Management 2011-04-04 01:54:56 UTC
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.

Comment 3 RHEL Program Management 2011-10-07 15:59:00 UTC
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.

Comment 13 errata-xmlrpc 2012-06-20 13:41:50 UTC
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


Note You need to log in before you can comment on or make changes to this bug.