Bug 688845

Summary:	NetworkManager should wait for interface initialization at start
Product:	Red Hat Enterprise Linux 6	Reporter:	Ian Kent <ikent>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED NOTABUG	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.3	CC:	igeorgex, mishu, rwheeler
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-14 23:39:48 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ian Kent 2011-03-18 08:18:05 UTC

Description of problem:

Some applications, such as autofs, need the network to be
available when they start. If the interface isn't available
these applications can experience problems.

I've tried a couple of times to add a retry on fail mechanism
to autofs but ran into odd problems both times.

This approach seems to be unnecessary anyway since the
NetworkManager init script has the ability to wait for this
completion anyway.

Could the NetworkManager init script wait for interfaces to
complete initialization by default?

What would be the downside of such a change?

Ian

Comment 2 RHEL Program Management 2011-04-04 02:01:06 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 Dan Williams 2011-06-14 23:39:48 UTC

Setting NETWORKWAIT=yes in /etc/sysconfig/network will activate this behavior.  If this does not work, please re-open this bug so we can diagnose.

Comment 4 Ian Kent 2011-06-15 02:51:39 UTC

(In reply to comment #3)
> Setting NETWORKWAIT=yes in /etc/sysconfig/network will activate this behavior. 
> If this does not work, please re-open this bug so we can diagnose.

I know that.

The reason for the bug is the steady stream of bugs that I get
because of this. That's why I posed the questions above which
I'd like answered.

I'd also like some suggestions as to what we can do to work around
this constant problem.