On 11/7/24 09:09, Bjørn-Helge Mevik via slurm-users wrote:

Bill via slurm-users slurm-users@lists.schedmd.com writes:

...

I want to confirm that the hostname resolution is case sensitive in SLURM ?

That should be easy enough to test:

$ sbatch -A nn9999k -t 10 --mem-per-cpu=100 --wrap='sleep 60' --nodelist=c3-1 Submitted batch job 13088180 $ sbatch -A nn9999k -t 10 --mem-per-cpu=100 --wrap='sleep 60' --nodelist=C3-1 sbatch: error: Batch job submission failed: Invalid node name specified

Looks like answer is Yes. :)

Thanks for the test, Bjørn-Helge! I can confirm with this example also looking up a node "a001":

# scontrol show node A001,a001 | head -2 Node A001 not found NodeName=a001 Arch=x86_64 CoresPerSocket=10

DNS can lookup this node without problems:

# host A001 a001.nifl.fysik.dtu.dk has address 10.2.129.1

Is Slurm's NodeName case sensitivity a bug or a feature? Maybe someone can shed light on this?

Thanks, Ole

On 11/7/24 10:47, Bjørn-Helge Mevik via slurm-users wrote:

Ole Holm Nielsen via slurm-users slurm-users@lists.schedmd.com writes:

...

Is Slurm's NodeName case sensitivity a bug or a feature?

Preventing people from using UPPERCASE hostnames, usernames, group names etc. is IMNSHO a feature. :D

Agreed :-) Just an added note on this question:

In the slurm.conf manual page is stated:

The contents of the file are case insensitive except for the names of nodes and partitions.

and under ClusterName:

Because of limitations in some databases, any upper case letters in the name will be silently mapped to lower case. In order to avoid confusion, it is recommended that the name be lower case.

/Ole