https://bugzilla.novell.com/show_bug.cgi?id=861489
https://bugzilla.novell.com/show_bug.cgi?id=861489#c20
--- Comment #20 from Andrey Borzenkov
The difference to the successful test you performed using a nfs entry in fstab and our setup is perhaps the higher complexity of our solution with more services involved. Our NFS mounts are done only via automounter, there are no NFS entries in fstab.
Yes. The problem is, if no filesystem that requires network is present in /etc/fstab, network-online.target IS NOT STARTED at all, so no synchronization point exists during shutdown. That is the weakest link here. The reasoning is - if nothing needs network, do not delay startup needlessly. But this contradicts "event based" systemd paradigm - we never know when network comes and goes. Currently if we unconditionally enable network-online.target this will pull in NetworkManager-wait-online.service for those that are using NM. By default it does not wait for anything, so it could be acceptable. Please try adding Wants: network-online.target to network@.service. This will ensure that when ifup is started it also starts network-online.target. NFS mounts should get dependency on it automatically. For ifup it has zero cost. You will need to restart network of course. But please consider that it is not strictly speaking systemd issue. Even assuming that all needed units are started - what happens when network *does* fail? There should be generic solution that covers situation of remote server being unavailable. But of course we need to fix the case of orderly shutdown. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.