Bugzilla – Bug 1217176
YaST NFS Client not enabling nfs-client.target
Last modified: 2024-05-27 07:38:21 UTC
A few days ago I did a fresh install of Tumbleweed. I used YaST NFS Client to create mount points for my nfs directories. I then noticed that the nfs directories would be unmounted after resuming a session from sleep mode. I would have to manually remount them. After some help from Arvidjaar in the forums we discovered nfs-client.target was disabled. After enabling nfs-client.target the problem has gone away and I find all nfs directories are mounted when resuming from sleep. YaST needs to enable nfs-client.target after creating nfs mount points. I just saw a similar bug report which has the status of fixed. If this is the same bug as previosly reported it is still unresolved. If not, I am reporting a new bug.
A first look into the source code did not show anything obvious. So please attach y2logs generated with the "save_y2logs" script. TIA.
I have checked it manually and I can confirm that the share is not mounted after resuming. Having the fstab entry has always been enough, but something has changed. We need to recheck how NFS should be configured nowadays. Maybe we need to add something like "x-systemd.automount" option in fstab.
I have tried adding the reqested yast log file 3 times without success. I keep getting a server error page. Is there another way to get this file to you? As previously stated, I executed 'systemctl enable nfs-client.target' after which my nfs directories auto mount returning from sleep. Totally fixed the problem.
The problem of "getting server error" seems to be described at https://github.com/yast/yast-yast2/issues/978 Long story short: save_y2logs script creates the archive with root-only access and your browser does not tell you. Then it simply uploads "nothing" and Bugzilla complains in her way: server error. Change the ownership of that resulting archive before uploading (`chown user:group file`).
No response for 3 months. Closing.