Yes, rpcbind is running and the nfs kernel modules are loaded. I’ve not changed the definition of the NFS targets in fstab on either machine. Also, one of them is a laptop that I use on different networks (home and office), and the NFS mounts fail in both environments.
Yes, it was reported multiple times and for different distros. It would be good if someone who experiences it and can provide information opened bug report for openSUSE. If you do it, post number here.
In the meantime the simplest workaround is to force NFSv3 (option vers=3) unless you really need NFSv4.
NFS works fine on 3 computers I have set-up as file-sharing servers on OS 13.1, so I would not agree proposing this as the general picture; these servers machines also work as clients. I manually mount them all though so the operational procedure might be different from yours, but they all do work. I have a forth machine running SuSE 9.1 as a NFS server on the LAN, and the three clients running 13.1 communicates quite fine that one as well.
I have exactly the same problem: same Kernel update, same dmesg about nfs4 and the mount error.
All was running ok on the client side: firewall setup, rpcbind and nfs client.
The nfs server was the exact same one from a previous nfs mount on that pc so the server could not be the problem.
I was getting frustrated when I started to search the net and made the recommended version 3 option on the mount command. It worked.
mount -t nfs mhtt:/mnt/data /mnt/util -v -o nfsvers=3,vers=3