My workplace was hit with this earlier this week (Upgrading from Ubuntu 20.04 -> 22.04.1). Just like to point out that KRB5CCNAME can refer to several different cache storage [alternatives](https://web.mit.edu/kerberos/krb5-1.12/doc/basic/ccache_def.html#ccache-types), for example I use `KEYRING:persistent:uidnumber` so an updated apparmor profile granting it access to `/tmp/krb5cc_*` would not solve it for me.
My workplace was hit with this earlier this week (Upgrading from Ubuntu 20.04 -> 22.04.1). Just like to point out that KRB5CCNAME can refer to several different cache storage [alternatives](https:/ /web.mit. edu/kerberos/ krb5-1. 12/doc/ basic/ccache_ def.html# ccache- types), for example I use `KEYRING: persistent: uidnumber` so an updated apparmor profile granting it access to `/tmp/krb5cc_*` would not solve it for me.