Bug 7203 - Inconsistent usage of "DefCpusPerGPU" vs. "DefCpuPerGPU"
Summary: Inconsistent usage of "DefCpusPerGPU" vs. "DefCpuPerGPU"
Status: RESOLVED INVALID
Alias: None
Product: Slurm
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 19.05.x
Hardware: Linux Linux
: --- 6 - No support contract
Assignee: Jacob Jenson
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2019-06-07 09:40 MDT by bugert
Modified: 2019-06-07 10:57 MDT (History)
0 users

See Also:
Site: -Other-
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bugert 2019-06-07 09:40:13 MDT 
Hi,

I just spent an hour trying to figure out why slurm 19.05 rejects our slurm.conf which uses the new "DefCpusPerGPU" parameter. Inspection of the config parser code revealed that slurm expects the parameter to be called "DefCpuPerGPU".

The wrongly spelled parameter is reported in many cases:

- in the slurm.conf documentation: https://github.com/SchedMD/slurm/blob/master/doc/man/man5/slurm.conf.5
- in the 19.05 release notes
- in the slides from SLUG 2018: https://slurm.schedmd.com/SLUG18/cons_tres.pdf

The scontrol documentation uses the correct spelling: https://github.com/SchedMD/slurm/blob/master/doc/man/man1/scontrol.1

Best regards,
Michael Bugert