[slurm-users] Conflicting --nodes and --nodelist

[Brian Andrus]

That is expected behavior as Marcus pointed out.

I suspect you may be doing something like targeting one of two systems 
that each have a node-locked license for some software, or have some 
different specs.

In this case, you may want to use the FEATURES option when defining 
those nodes and then request that feature when submitting your job.

Brian Andrus


On 6/1/2021 4:15 AM, Diego Zuccato wrote:
> Hello all.
>
> I just found that if an user tries to specify a nodelist (say 
> including 2 nodes) and --nodes=1, the job gets rejected with
> sbatch: error: invalid number of nodes (-N 2-1)
> The expected behaviour is that slurm schedules the job on the first 
> node available from the list.
> I've found conflicting info about the issue. Is it version-dependant?
> If so, we're currently using 18.08.5-2 (from Debian stable). Should we 
> expect changes when Debian will ship a newer version? Is it possible 
> to have the expected behaviour?
>
> Tks.
>