Closed dingp closed 1 year ago
If using AL9 release, when doing klist or kinit, one would end with:
klist
kinit
klist: Unknown credential cache type while resolving ccache
This is caused by the fact that the binaries did not link against libkeyutils.so.
libkeyutils.so
We did not have this issue with ext-v1.1 because the docker image we used to build the stack have libkeyutils.so in its system path.
ext-v1.1
There are two ways to fix/bypass this issue:
keyutils-libs-devel
krb5
keyutils
export KRB5CCNAME=$(mktemp)
Implemented 1, this should fix the issue for now.
Do not plan to implement 2, but leave it to spack upstream to fix it.
If using AL9 release, when doing
klist
orkinit
, one would end with:klist: Unknown credential cache type while resolving ccache
This is caused by the fact that the binaries did not link against
libkeyutils.so
.We did not have this issue with
ext-v1.1
because the docker image we used to build the stack havelibkeyutils.so
in its system path.There are two ways to fix/bypass this issue:
keyutils-libs-devel
into the external software stack, and makekrb5
dependent on it;krb5
in spack using a docker container wherekeyutils
is installed;export KRB5CCNAME=$(mktemp)
, and thenkinit
on AL9 nodes where kerberized ssh is required.