Bug 813160

Summary:	Starts to early for network services.
Product:	[Fedora] Fedora	Reporter:	Robin Laing <mesat>
Component:	autofs	Assignee:	Ian Kent <ikent>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	ikent, sigbjorn
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-15 04:12:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Robin Laing 2012-04-17 06:11:47 UTC

Description of problem:
Autofs starts before all network services are ready.  Remote drives are not selected until autofs is restarted.

Version-Release number of selected component (if applicable):
autofs-5.0.6-5.fc16.x86_64

How reproducible:
Every reboot.

Steps to Reproduce:
1. Shutdown or restart machine.
2. Try to login using ldap and remote home directories.
3. Home directory not found.
  
Actual results:
Home directory is not mounted as expected.

Expected results:
Home directory should be mounted via autofs after a reboot without having to restart the service.

Additional info:
Once the boot/reboot sequence is completed, if I restart autofs (service autofs restart).  Everything works as expected.  In the past I would just change the number for the boot start-up but it has been changed back on a reboot or upgrade.

Comment 1 Ian Kent 2012-04-17 09:47:22 UTC

Assuming you are using NetworkManager, try enabling the 
NetworkManager-wait-online.service.

I believe NetworkManager will return control to systemd
before the network is actually available.

Comment 2 Robin Laing 2012-05-15 04:12:15 UTC

I finally got a chance to test this on the affected machine.

NetworkManager-wait-online.service

Seems to have fixed the problem.  I guess there are lots of things to learn with the move to systemd.

I guess this is really not a bug but a change in how the system boots.  Changing the process number didn't work as before.

Comment 3 Ian Kent 2012-09-20 00:56:42 UTC

*** Bug 858848 has been marked as a duplicate of this bug. ***