NFS does not mount automatically, root access required

Hallo Community,

I recently had purchased a new mini-PC with pre-installed OpenSuse Leap 15.1 from TUXEDO.

This unit behaves different, then other machines I have in my network.

Environment:
NFS Server: Synology Disk-Station DSM 6.2.2-24922 Update 4

The machines I installed myself (All Leap 15.1, from network installation)
/etc/fstab

...
THOT03.local:/volume1/production           /home/zzz_servers/thot03  nfs    defaults                      0  0
THOT03.local:/volume1/abc                /home/zzz_servers/thot03_abc  nfs    defaults                      0  0
THOT03.local:/volume1/def                /home/zzz_servers/thot03_def  nfs    defaults                      0  0
THOT03.local:/volume1/ghi            /home/zzz_servers/ghi  nfs    defaults                      0  0

The new machine: (Leap 15.1 preinstalled)

...
THOT03.local:/volume1/production           /home/zzz_servers/thot03  nfs    defaults                      0  0
THOT03.local:/volume1/abc                /home/zzz_servers/thot03_abc  nfs    defaults                      0  0
THOT03.local:/volume1/def                /home/zzz_servers/thot03_def  nfs    defaults                      0  0
THOT03.local:/volume1/ghi            /home/zzz_servers/ghi  nfs    defaults                      0  0

UID’s are Identical at the machines, and I cant find any group assignment at my installations that are superior.

The machines installed by me show the nfs-shares active (monted) for the users (all users) after log in, while the TUXEDO machine shows the mounts, but inactive (unmounted).
To make it working one has to login as root (or sudo) and mount the nfs shares first, before they get available for the users.

I sent a support request to TUXEDO but they can’t explain the behavior.

May be sombody has a tipp, where I can start my evaluation.

Thanks
Bert

Do you use NeworkManager or wicked for network configuration?

Thank you for your reply.
It is networkmanager.

  1. To mount NFS automatically on boot connection must be system (or available to all users), not user specific.
  2. You need to enable NetworkManager-wait-online.service to ensure interface is up before system attempts mounting remote filesystem.

NetworkManager-wait-online.service was missing. With this enabled it worked as expected.

Thank you!
Bert