Ticket 4325 - sacctmgr dump output doesn't contain QOS settings
Summary: sacctmgr dump output doesn't contain QOS settings
Status: OPEN
Alias: None
Product: Slurm
Classification: Unclassified
Component: Accounting (show other tickets)
Version: 17.11.x
Hardware: Linux Linux
: 5 - Enhancement
Assignee: Unassigned Developer
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2017-11-01 10:47 MDT by Ben Matthews
Modified: 2023-10-19 14:39 MDT (History)
2 users (show)

See Also:
Site: UCAR
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
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: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
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=..."