Bug 477045

Summary:	ypbind hangs at boot time when NetworkManager is turned on
Product:	[Fedora] Fedora	Reporter:	Ed Friedman <edfriedmangvs>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	dcbw, kevarh, wtogami
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:	2009-02-13 15:31:16 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 Ed Friedman 2008-12-18 20:39:49 UTC

Description of problem:
ypbind hangs at boot time when NetworkManager is turned on

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.12.svn4326.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1.Turn on NetworkManager with ntsysv
2.Turn on ypbind with ntsysv
3.Reboot computer
  
Actual results:
ypbind hangs for many minutes during bootup and eventually the computer starts up with ypbind not running

Expected results:
ypbind should start up normally

Additional info:
ypbind starts normally when network is used instead of NetworkManager.  Also, even though NetworkManager and ypbind have S27 for startup, NetworkManager defintely starts up first.  Network has S10 for startup and moving NetworkManager to S10 does not fix this problem.

Comment 1 Kevin Arhelger 2009-02-03 05:21:07 UTC

Same issue with nfslock and messagebus.
Network manager starts to late in the boot process.

Comment 2 Dan Williams 2009-02-13 12:13:48 UTC

What levels do nfslock and ypbind start at?  They'll need to start somewhat later, or we need to switch to a startup dependency system that can handle this stuff.

Comment 3 Kevin Arhelger 2009-02-13 14:59:12 UTC

Chkconfig says nfslock starts at levels 2345.
This box has ldap authentication and an nfs home directory.

I was able to work around by adding network to runlevels 2345 and disabling NetworkManager.

Comment 4 Dan Williams 2009-02-13 15:31:16 UTC

Ok; I think we'll simply have to revisit this when our startup process gets more intelligent, and we can actually make stuff like ypbind wait on the network actually coming up.