[slurm-users] Weirdness with partitions

[Diego Zuccato]

Hello all.

We have one partition (b4) that's reserved for an account while the 
others are "free for all".
The problem is that
sbatch --partition=b1,b2,b3,b4,b5 test.sh
fails with
sbatch: error: Batch job submission failed: Invalid account or 
account/partition combination specified
while
sbatch --partition=b1,b2,b3,b5 test.sh
succeeds.

Shouldn't Slurm (22.05.6) just "filter out" the inaccessible partition, 
considering only the others?
Just like what it does if I'm requesting more cores than available on a 
node.

I'd really like to avoid having to replicate scheduler logic in 
job_submit.lua... :)

-- 
Diego Zuccato
DIFA - Dip. di Fisica e Astronomia
Servizi Informatici
Alma Mater Studiorum - Università di Bologna
V.le Berti-Pichat 6/2 - 40127 Bologna - Italy
tel.: +39 051 20 95786