User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
Firefox/60.0
Build Identifier: 

I have a laptop system that has in its /etc/exports file:
   /MyLib 
192.168.2.0/24(fsid=0,crossmnt,rw,no_root_squash,async,no_subtree_check,insecure)
   /MyDisk
192.168.2.0/24(fsid=1,crossmnt,rw,no_root_squash,async,no_subtree_check,insecure)
I can mount these from a NFS client without issues.
In the /etc/fstab I have on the client
   server:/MyLib /MyLib nfs noauto,user 0 0
   server:/MyDisk /MyDisk nfs noauto,user 0 0

Next i unmount the file systems on the client and then i suspend the server
system with "systemctl suspend".

When i next startup/resume the server again I can no longer mount the file
systems. Mount fails with:
   mount.nfs: requested NFS version or transport protocol is not supported

Rebooting the nfs client doesn't help. Only a reboot of the server make the
error go away.

Both the server and the client are running Leap 15 and are at the latest
patches (17 Dec 2018)

Before, when i was running Leap 42.3 on both, this worked OK. 

Reproducible: Always

Steps to Reproduce:
1.On an NFS client, mount /MyLib
2.On that NFS client, unmount /MyLib again
3.Suspend the NFS server = do as root: systemctl suspend
4.Startup/resume the server
5.try step 1
Actual Results:  
step 5 fails with "mount.nfs: requested NFS version or transport protocol is
not supported"
rebooting the NFS client doesn't help, rebooting the server does.

Expected Results:  
successful mount

this is a regression from Leap 42.3, 42.2 and 42,1 where this scenario worked
OK.

I run NFS services on an old laptop and use it to serve out movies/pictures to
a Minix player. I also use it as a backup server for my Leap systems. However i
don't want to keep it running 24x7.