Comment 7 for bug 1956787

NFS is comprised of many services (specially on nfsv3), and they differ whenever v3 or v4 is used. The packaging tries to make the right choices, and goes through many hoops for that.

In summary, you should have nfs-server.service enabled on the server, and nfs-client.target (target!) on the client, and the correct services should come up after boot. You can even do "systemctl restart nfs-server" on the server and the correct services should be restarted in the right order.

The client target has this note:

 nfs-client.target
    If enabled, daemons needs for an nfs client are enabled.
    This does *not* include rpc.statd. the rpc-statd.service unit
    is started by /usr/sbin/start-statd which mount.nfs will run
    if statd is needed.

I wonder if that script isn't working, or not being called in your case for some reason.