Bug 234582

Summary:	dhcp time-out when no signal on cable
Product:	[Fedora] Fedora	Reporter:	Taco Witte <info>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	low	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-04-12 18:53:40 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 Taco Witte 2007-03-30 10:04:57 UTC

Description of problem:
After installing a second NIC, DHCP is run on startup when there's no signal on
the cable. This adds 20 seconds or so to boot time.

Version-Release number of selected component (if applicable):
Fedora 7 test 3, updated as of March 30

Expected result:
The DHCP daemon should see that there's no signal on the cable and terminate
directly.

Comment 1 David Cantrell 2007-04-05 17:38:10 UTC

This is happening because of something in initscripts.  The settings in
/etc/sysconfig/network-scripts/ifcfg-* are being ignored for some reason and the
network service is running DHCP for everything.

Reassigning.  See also bug #234764.

Comment 2 Bill Nottingham 2007-04-06 03:26:11 UTC

What's your ifcfg file?

Comment 3 Taco Witte 2007-04-11 11:34:13 UTC

There's a chance that this bug doesn't exist after all. The (secondary, eth1)
NIC on which this error occurred is dead now, so maybe it was dying back then.
Sorry for the wasted time in that case.

If there's a problem, it's probably this: running "dhclient eth0" by hand waits
forever when there's no signal, while running DHCP through Network Confguration
and /etc/init.d/networking correctly terminates with the message that there's no
signal on the cable.

I don't have the original configuration files anymore alas.

Comment 4 Bill Nottingham 2007-04-11 19:41:22 UTC

dhclient doesn't do a link check, so it may wait forever (modulo whatever normal
dhcp timeouts it has). The ifup script that calls dhclient is what has the link
test.

However, this particular issue (networking going strange on first bootup) has
been reported enough that it's obviously a real issue.

Comment 5 Bill Nottingham 2007-04-12 18:53:40 UTC


*** This bug has been marked as a duplicate of 234764 ***