Bug 1318012 - graphical-target requires network for autofs home directories
Summary: graphical-target requires network for autofs home directories
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 18:25 UTC by Bill Quayle
Modified: 2016-04-15 06:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-15 06:13:00 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bill Quayle 2016-03-15 18:25:57 UTC 
Description of problem:
When the default.target is graphical.target, and the user home directories are autofs/NFS-mounted filesystems, NetworkManager.service should be required before the graphical desktop is presented.

Version-Release number of selected component (if applicable):
CentOS/RHEL/Fedora > 7.0

How reproducible:
Always

Steps to Reproduce:
1. Load OS
2. Configure autofs client or fstab-based NFS mount of user home directories
3. Enable graphical desktop

Actual results:
User is unable to login to desktop, because the desktop is presented before the network and automount/nfs become available.

Expected results:
User is able to login to their nfs-mounted home directory.

Additional info:
Comment 2 Lukáš Nykrýn 2016-03-16 09:40:46 UTC 
Unfortunately it is up to you to enable NM, network.service, or systemd-networkd. Systemd only provides synchronization points, so those services are started in correct order.
Comment 3 Michal Sekletar 2016-03-17 08:40:28 UTC 
Please provide exact systemd version which exhibits the problem. Did you change default configuration in any way (well except enabling autofs)? If yes, please outline changes you've have made. Also attach output of "journalctl -b" after you reproduce the issue.
Note You need to log in before you can comment on or make changes to this bug.