Bug 191137

Summary:	check_link_down timeout is too short
Product:	Red Hat Enterprise Linux 4	Reporter:	John Newbigin <jn>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NEXTRELEASE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-08-01 15:18:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Newbigin 2006-05-09 04:07:51 UTC

Description of problem:
the check_link_down function in /etc/sysconfig/network-scripts/network-functions
is too short for our network.  We are on a Cisco Catalyst 4507R and it takes
ages for the link to come up.

Version-Release number of selected component (if applicable):
7.93.24.EL-1.1

How reproducible:
Most of the time

Steps to Reproduce:
1. Configure eth0 to dhcp
2. run "ifup eth0"
3.
  
Actual results:
Determining IP information for eth0... failed; no link present.  Check cable?

Expected results:
Determining IP information for eth0... done.

Additional info:
Our temporary fix is to change
while [ $timeout -le 10 ]; do
into 
while [ $timeout -le 20 ]; do

This file is marked as a config file so it is OK if we update, but this should
have a better default, or at least be user configurabe.

Comment 1 Bill Nottingham 2006-08-01 15:18:05 UTC

This will be fixed for RHEL 5 via the LINKDELAY parameter.

Red Hat does not currently plan to provide a resolution for this in a Red Hat
Enterprise Linux update for currently deployed systems.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects.