Created attachment 10415 [details] slurmctld log file of the described scenario When a user launches jobs with hold parameter and QOS which has MaxJobsPU limit, then jobs hold with reason JobHeldAdmin instead of JobHeldUser. This happens in the following situation: 1) The user submits more than QOSMaxJobsPerUserLimit jobs in hold state. 2) The user releases his held jobs, some of them start to run, some are pending with QOSMaxJobsPerUserLimit reason. 3) At the same moment the user submits new hold jobs. And these new jobs are held with JobHeldAdmin reason. In the attachment we provide the slurmctld log related to this situation and jobinfo for one of job (109015) which was held with reason JobHeldAdmin.
Created attachment 10416 [details] jobinfo file
Hi Thanks for reporting this, I can reproduce this. I will let you know when the fix will be in the repo. Dominik
Hi This commit fixed this issue it will be in 19.05.1 and above. https://github.com/SchedMD/slurm/commit/fe8226e72 I'll go ahead and close this. Thank you. Dominik