Bug 625837

Summary:	systemd isn't starting networkmanager at boot time
Product:	[Fedora] Fedora	Reporter:	Jeff Layton <jlayton>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14	CC:	lpoetter, metherid, mschmidt, notting, plautrba, steved
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:	2010-08-20 20:42:14 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 Jeff Layton 2010-08-20 15:14:31 UTC

Upgraded my laptop to f14 alpha and patched it with yum update (after having to manually upgrade yum to the f14 version when anaconda didn't do it).

Now when I boot, it doesn't start NetworkManager and I have no network interfaces. NetworkManager is chkconfig'ed on. Manually running "service NetworkManager start" works around the problem.

$ chkconfig --list NetworkManager
NetworkManager 	0:off	1:off	2:on	3:on	4:on	5:on	6:off

$ rpm -q systemd NetworkManager
NetworkManager-0.8.1-4.git20100817.fc14.x86_64
systemd-7-3.fc14.x86_64

Comment 1 Jeff Layton 2010-08-20 16:33:26 UTC

Might be a duplicate of bug 625386, but Harald's fix didn't work for me...

Comment 2 Rahul Sundaram 2010-08-20 20:42:14 UTC


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