I'm booting a VM guest that needs to bring up an NFS mount. Right now on boot, something's out of order and it fails ... [ OK ] Started wicked network management service daemon. [ 23.805688] systemd[1]: Started wicked network management service daemon. [ 23.834962] systemd[1]: Starting wicked network nanny service... Starting wicked network nanny service... [FAILED] Failed to start Alias for NFS client. See "systemctl status nfs.service" for details. [ 23.876106] systemd[1]: Failed to start Alias for NFS client. [ OK ] Started System Logging Service. [ OK ] Started wicked network nanny service. ... Checking systemctl status nfs.service -l nfs.service - Alias for NFS client Loaded: loaded (/usr/lib/systemd/system/nfs.service; enabled) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: failed (Result: exit-code) since Tue 2016-01-26 07:16:26 PST; 52s ago Process: 738 ExecStop=/usr/bin/umount -aft nfs,nfs4 (code=exited, status=0/SUCCESS) Process: 727 ExecStartPost=/usr/bin/mount -at nfs,nfs4 (code=exited, status=32) Process: 705 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 705 (code=exited, status=0/SUCCESS) Jan 26 07:16:26 linux-u398 mount[727]: mount.nfs4: Failed to resolve server nfs01.example.com: Name or service not known That server's the mount defined in the guest's /etc/fstab cat /etc/fstab ... nfs01.example.com:/SEC/clients/client06 /sec/client06 nfs4 _netdev,tcp,ro,auto,soft,async,noexec,nosuid,bg,rsize=32768,wsize=32768 0 0 IIUC, fstab entries are translated by systemd-fstab-generator into native systemd units durint early boot, and it's systemd that controls the mounts & their dependencies. But, here, wicked's also involved as another layer. *Something* needs to wait longer on boot. I think just waiting for network to be online is good enough maybe? Question is -- what unit needs the additional dependency? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org