What were you trying to do that didn't work?

This affects all existing releases.

In a Kerbersized mount, the client's mount fails after the server's credentials have been updated at the KDC and it signals that via sending KRB5_AP_ERR_BAD_INTEGRITY error during GSS context establishment.

This problem has been fixed in nfsutils's gssd but when running with use-gss-proxy=1 it leads to failure.

Please provide the package NVR for which bug is seen:

How reproducible:

Steps to reproduce

1. mount -o sec=krb5 <server>:/<volume> <mount point>
2. umount 
3. update server's key tab at KDC. Upload new key tab to the server
4. mount -o sec=krb5 <server>:/<volume> <mount point> this step leads to failure because gssproxy uses existing nfs ticket and the is unable to handle receiving BAD_INTEGRITY error to use the tgt again to get the new service ticket.

Expected results

mount shouldn't fail.

Actual results