I'm seeing a weird issue when I try to increase limits on a child account that a coordinator has created. Here is the setup:
1. Create an account named slurm_parent, set coordinator1 as a coordinator of that account, and give that account a grptresmins=cpu=100 limit. 2. As coordinator1, create a child account named slurm_child whose parent is slurm_parent. 3. As coordinator1, set the grptresmins=cpu=10 limit on the child account.
That all works fine. The problem is when I try to INCREASE the cpu limit on the child account by any amount.
$coordinator1> sacctmgr modify account test_crch_slurmaccessch set grptresmins=cpu=11
sacctmgr: error: Coordinators can not increase job limits beyond the parent ones Modified account associations... Error with request: Coordinators can not increase job limits beyond the parent ones
The first issue is that the limit of cpu=11 is NOT beyond the parent limit of cpu=100.
The second issue is that (as a workaround), I can remove the cpu=10 limit on the child account as coordinator (by setting it to -1), and then I can set grptresmins=cpu=1000. That command works. So, I can very clearly set a grptresmins=cpu limit that is beyond the parent limit (I understand that the child account in reality won't be able to access more than the parent account, no matter what the limit is).
Note that as coordinator, I can REDUCE the limit on the child account all I want. So I can set it to cpu=9 just fine. But if I try to set it back to 10, I'll again get the error saying I can't go above parent limits.
So here are my issues:
1. Inability of coordinator to increase the child account grptresmins limits once set. 2. Incorrect error message about exceeding the parent limit.
I originally saw this issue on 24.11.6, and built and tested on 25.11.3, and still see the issue.
Thanks for any help figuring out what I'm doing wrong.
Rob
Ooops....in my error message command example, I used the account I had actually been using (test_crch_slurmaccessch), not the madeup account (slurm_child) for the email. Disregard that, the error message is what shows no matter which child account you use. ________________________________ From: Groner, Rob via slurm-users slurm-users@lists.schedmd.com Sent: Tuesday, February 24, 2026 11:17 AM To: Cristóbal Navarro via slurm-users slurm-users@lists.schedmd.com Subject: [slurm-users] Issue with coordinator increasing limits
I'm seeing a weird issue when I try to increase limits on a child account that a coordinator has created. Here is the setup:
1. Create an account named slurm_parent, set coordinator1 as a coordinator of that account, and give that account a grptresmins=cpu=100 limit. 2. As coordinator1, create a child account named slurm_child whose parent is slurm_parent. 3. As coordinator1, set the grptresmins=cpu=10 limit on the child account.
That all works fine. The problem is when I try to INCREASE the cpu limit on the child account by any amount.
$coordinator1> sacctmgr modify account test_crch_slurmaccessch set grptresmins=cpu=11
sacctmgr: error: Coordinators can not increase job limits beyond the parent ones Modified account associations... Error with request: Coordinators can not increase job limits beyond the parent ones
The first issue is that the limit of cpu=11 is NOT beyond the parent limit of cpu=100.
The second issue is that (as a workaround), I can remove the cpu=10 limit on the child account as coordinator (by setting it to -1), and then I can set grptresmins=cpu=1000. That command works. So, I can very clearly set a grptresmins=cpu limit that is beyond the parent limit (I understand that the child account in reality won't be able to access more than the parent account, no matter what the limit is).
Note that as coordinator, I can REDUCE the limit on the child account all I want. So I can set it to cpu=9 just fine. But if I try to set it back to 10, I'll again get the error saying I can't go above parent limits.
So here are my issues:
1. Inability of coordinator to increase the child account grptresmins limits once set. 2. Incorrect error message about exceeding the parent limit.
I originally saw this issue on 24.11.6, and built and tested on 25.11.3, and still see the issue.
Thanks for any help figuring out what I'm doing wrong.
Rob
-
Groner, Rob