t you have configured
> authentication using AD on your head node.
> BUT you have not confiured it ont he compute node images. You probably
> have to prepare a new compute node image then push that otu to the compute
> nodes.
>
>
>
>
>
>
>
>
>
&g
t and the su to the AD user to make sure that the node
>> is integrated correctly?
>>
>> If you cannot su to an AD user on the node then Slurm will not be able to
>> resolve the UID either as they use the same methods.
>>
>>> On Wed, 13 Feb 2019, 12:35
en similar issues on AD integrated systems where some nodes boot from
> a different image that have not yet been joined to the domain.
>
> Antony
>
>> On Wed, 13 Feb 2019 at 04:58, Yugendra Guvvala
>> wrote:
>> Hi,
>>
>> We are bringing a new cluster
nt image that have not yet been joined to the domain.
>
> Antony
>
>> On Wed, 13 Feb 2019 at 04:58, Yugendra Guvvala
>> wrote:
>> Hi,
>>
>> We are bringing a new cluster online. We installed SLURM through Bright
>> Cluster Manager how ever we are runn
Hi Loris,
Thank you, this is strange. Is there a way to integrate AD authentication with
SLURM or Munge. Or allow all users who login to run jobs with out any
restrictions .
Thanks,
Yugi
> On Feb 13, 2019, at 1:50 AM, Loris Bennett wrote:
>
> Yugendra Guvvala writes:
>
>&
Hi, We are bringing a new cluster online. We installed SLURM through Bright Cluster Manager how ever we are running into a issue here. We are able to run jobs as root user and users created using bright cluster (cmsh commands). How ever we use AD authentication for all our users and when we try to
