After upgrading from precise to trusty, I started seeing the following error messages in the logs whenever there was Kerberized NFS activity:
Jun 17 08:02:43 hostname rpc.gssd[1021]: ERROR: GSS-API: error in gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been established) - Unknown error
Jun 17 08:02:43 hostname rpc.gssd[1021]: WARN: failed to free lucid sec context
I've determined this to be a regression introduced (into upstream release 1.2.8) by commit 051eb4863cf880f0349a1de44517f9c99a9c5bd4. The bug is still present in upstream release 1.3.0. I've successfully tested the attached, obvious patch.
After upgrading from precise to trusty, I started seeing the following error messages in the logs whenever there was Kerberized NFS activity:
Jun 17 08:02:43 hostname rpc.gssd[1021]: ERROR: GSS-API: error in gss_free_ lucid_sec_ context( ): GSS_S_NO_CONTEXT (No context has been established) - Unknown error
Jun 17 08:02:43 hostname rpc.gssd[1021]: WARN: failed to free lucid sec context
I've determined this to be a regression introduced (into upstream release 1.2.8) by commit 051eb4863cf880f 0349a1de44517f9 c99a9c5bd4. The bug is still present in upstream release 1.3.0. I've successfully tested the attached, obvious patch.