Ticket 4226

Summary: GrpTRES CPU limit is case sensitive
Product: Slurm Reporter: Ole.H.Nielsen <Ole.H.Nielsen>
Component: LimitsAssignee: Director of Support <support>
Status: RESOLVED FIXED QA Contact:
Severity: 4 - Minor Issue    
Priority: --- CC: brian
Version: 17.02.7   
Hardware: Linux   
OS: Linux   
Site: DTU Physics 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: 17.02.8 Target Release: ---
DevPrio: --- Emory-Cloud Sites: ---
Attachments: updated docs for resource limits

Description Ole.H.Nielsen@fysik.dtu.dk 2017-10-06 08:01:31 MDT 
I'm updating our user limits (GrpTRES, GrpTRESRunMins) with a local script and encountered this error message:

# sacctmgr modify user where name=mabr set GrpTRES=CPU=1500
 Unknown option: GrpTRES=CPU=1500
 Use keyword 'where' to modify condition

It turns out that "GrpTRES=CPU=1500" must be changed into "GrpTRES=cpu=1500" with lower-case "cpu".

I haven't been able to find any documentation pages defining the syntax of GrpTRES, GrpTRESRunMins and giving detailed examples.  So the case sensitivity seems confusing here.  The page https://slurm.schedmd.com/resource_limits.html has no such examples.

Questions: 
Could the documentation be updated to define clearly, and give examples of, such limits?  
Could/should limits such as the above made case insensitive (using a tolower() function internally)?

FYI: I think we have the default TRES defined:

# sacctmgr show tres 
    Type            Name     ID 
-------- --------------- ------ 
     cpu                      1 
     mem                      2 
  energy                      3 
    node                      4
Comment 9 Isaac Hartung 2017-10-10 13:21:31 MDT 
Created attachment 5362 [details]
updated docs for resource limits