Replies: 2 comments 1 reply
-
OK, so I've made some progress. It seems that querying the api the 'user_name' field is not populated on the slurmrestd I'm running on my slurm-web host, but it is populated on my 'other' api hosts. I'm unsure why there's a discrepancy here, but I'll dig deeper to figure out why the config seems to behave differently. (Pondering if it's to do with the authentication modes/JWT keys) |
Beta Was this translation helpful? Give feedback.
-
And to answer my question finally - I did finally track it down using different slurm-api responses. It's to do with the host local user database - the API returns UID and GID just fine, but won't resolve them if they're not 'valid' on the slurm-web host - even if, seemingly, I've configured the gateway.ini LDAP, the slurmrestd is upstream of that and needs to be able to resolve the userids (via the same LDAP) it seems. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've gone through the troubleshooting steps I can think of - like check the LDAP config is good, but I don't think this is ldap related.
On the 'jobs list' the column User (account) is only listing entries of (account).
E.g. Instead of
myname(sysadmin) it's just showing (sysadmin).
But if I click on the job info the 'user' and 'account' fields are correctly populated - but the group isn't. But the slurm API does seem to be returning this too (and the agent.ini _ think shouldn't be filtering 'group_name' out?)
So I'm wondering where I should look to figure out what's wrong.
Beta Was this translation helpful? Give feedback.
All reactions