Bug 738448

Summary:	kdm started before nfs home directory is mounted
Product:	[openSUSE] openSUSE 12.2	Reporter:	H Markert <mephisto>
Component:	Basesystem	Assignee:	Frederic Crozat <fcrozat>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	suse-beta
Version:	Factory
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description H Markert 2011-12-23 15:33:30 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0

I am using openSUSE 12.1 (kde4) with home directory mounted through NFSv4 with kerberos security.
When booting the system, kdm is started and ready to use long before the NFS mount becomes available. If the user tries to login as soon as kdm is ready, login fails because the home directory is not yet available.
After kdm appears ready to use, it takes about 30s until /home gets mounted. After waiting long enough, login is possible.

As workaround, sysvinit can be used with package sysvinit-init or with init=/sbin/sysvinit kernel parameter. Sysvinit booting works as expected.

Reproducible: Always

Steps to Reproduce:
1. Install SuSE with home on nfs
2. Reboot
3. log in as soon as graphical login manager becomes available. 

Actual Results:  
Login fails, /home/USER is not available

Expected Results:  
successful login.

Comment 1 Christian Boltz 2011-12-23 22:58:18 UTC

"Sysvinit booting works as expected." means this is probably a systemd issue.

Comment 2 Frederic Crozat 2012-01-27 13:16:18 UTC

what is the output of :
systemctl is-enabled nfs.service
systemctl status nfs.service
systemctl status remote-fs.target

?

(please retest with all 12.1 maintenance update applied).

Comment 3 H Markert 2012-01-30 18:37:49 UTC

It's working for me now with all updates installed.

However, after switching back from sysvinit sssd did not come up, although it was enabled in Yast/system services.
I disabled and re-enabled it there, rebooted the system, and now everything seems to be working as expected.

Comment 4 Frederic Crozat 2013-03-11 15:53:39 UTC

closing as fixed