Comment 2 for bug 1807749

> As far as I understand my setup, I do not have DNS before nss_ldap
> is started.

nss_ldap is not "started". It is a module which is loaded into the memory of processes that need to resolve user and group names; error messages in your log about nss_ldap are caused by attempts to look up usernames before your network is configured.

In general, if you want robust LDAP and Kerberos operation on a host in the face of possible network disconnection, it's recommended that you use the sssd package instead of using nss_ldap directly.

As for your NFS mount failure, it is quite possible that the NFS mount is being attempted at boot before DNS resolution is available. The relevant bits of output in this log file are:

Dez 10 18:07:03 barney systemd[1]: Started Network Manager Wait Online.
Dez 10 18:07:03 barney systemd[1]: Reached target Network is Online.
[...]
Dez 10 18:07:03 barney systemd[1]: home.mount: Directory /home to mount over is
not empty, mounting anyway.
Dez 10 18:07:03 barney systemd[1]: Mounting /home...
[...]
Dez 10 18:07:03 barney mount[1803]: mount.nfs4: Failed to resolve server nfs.server: Name or service not known
Dez 10 18:07:03 barney mount[1800]: mount.nfs4: Failed to resolve server nfs.server: Name or service not known

So the issue is that network-manager is reporting to systemd that the network is "online", but DNS resolution of nfs.server still fails.

I believe this is a bug in the definition of NetworkManager-wait-online.service, which needs to block until not only packets can pass on an interface, but also DNS resolution works.