Ticket 4325

Summary: sacctmgr dump output doesn't contain QOS settings
Product: Slurm Reporter: Ben Matthews <matthews>
Component: AccountingAssignee: Unassigned Developer <dev-unassigned>
Status: OPEN --- QA Contact:
Severity: 5 - Enhancement    
Priority: --- CC: niko.luke, sts
Version: 17.11.x   
Hardware: Linux   
OS: Linux   
See Also: https://bugs.schedmd.com/show_bug.cgi?id=7450
https://bugs.schedmd.com/show_bug.cgi?id=9111
Site: UCAR Slinky Site: ---
Alineos Sites: --- Atos/Eviden Sites: ---
Confidential Site: --- Coreweave sites: ---
Cray Sites: --- DS9 clusters: ---
Google sites: --- HPCnow Sites: ---
HPE Sites: --- IBM Sites: ---
NOAA SIte: --- NoveTech Sites: ---
Nvidia HWinf-CS Sites: --- OCF Sites: ---
Recursion Pharma Sites: --- SFW Sites: ---
SNIC sites: --- Tzag Elita Sites: ---
Linux Distro: --- Machine Name:
CLE Version: Version Fixed:
Target Release: --- DevPrio: ---
Emory-Cloud Sites: ---

Description Ben Matthews 2017-11-01 10:47:13 MDT 
If QOS is in use, a file produced by "sacctmgr dump" can't be loaded into a fresh database, since sacctmgr doesn't dump the actual qos levels, but does reference them.

sacctmgr load file=... cluster=...
....
sacctmgr: error: You gave a bad qos '...'. Valid QOS's are normal
Comment 1 Ben Matthews 2017-11-01 10:53:21 MDT 
just to be clear, the file was generated by doing something like

"sacctmgr dump file=... cluster=..."