NFS mounts with Kerberos fail at boot after upgrade to leap 16

Hi all,

I am about to upgrade our systems from leap15-6 to leap-16. The main parts of our setup are the following. The linux clients are members of an Windows AD domain using samba-winbind. There is a debian fileserver in the domain providing NFS exports secured with krb5p for our clients. The clients mount the nfs mounts with krb5p option via fstab at boot.

Everything works fine with leap 15.6. When i use the same config with leap 16 the mounts fail at boot. I figured out that I have to manually restart the service rpc-gssd.service and mount the shares manually to get it working again after reboot. The service starts during boot but stops again.

Winbind and the keytab are working correctly after reboot and should not be the problem.

I am aware of the possibility to add dependencies to systemd services to control their boot order. But I do not know which dependency is missing here. Also, i guess a change like that should not be neccessary to get a standard nfs4 kerberos mount working, should it? Am I missing something in the nfs or kerberos config that changed with leap 16?

I hope one of you is using a sinilsr setup and xan help me with this.

Thank you very much.

Gregor