Something to try . .
If you restart “slurmctld” does the new QOS apply?
We had a situation where slurmdbd was running as a different user than
slurmctld and hence sacctmgr changes weren’t being reflected in slurmctld.
-greg
On 27 Apr 2020, at 12:57, Simon Andrews
mailto:simon.andr...@babr
Try suspending and resuming the users pending jobs to force a re-evaluation.
If the user is not in the zone of jobs that is evaluated, ie if enough higher
priority jobs have dropped in ahead then this job may not have been evaluated
for scheduling since a point in time when the user was indeed p
