| Summary: | Failed to add association by coordinator | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Maxim Syrchin <msyrchin> |
| Component: | Database | Assignee: | Jacob Jenson <jacob> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | 6 - No support contract | ||
| Priority: | --- | CC: | cfzaruba, jonathon.anderson |
| Version: | 17.02.9 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | -Other- | 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: | --- | ||
Seeing the same in 17.11.5. I believe the underlying issue is that coordinator rights aren't created/inherited when sub-accounts are created by the parent coordinator. Observed behavior: Coordinator creates sub-account Coordinator adds user to sub-account, fails Coordinator attempts to add self as sub-account coordinator, fails root adds Coordinator to sub-account Coordinator adds user to sub-account, succeeds We are experiencing this behavior with 20.02.4 as well. Could this be fixed? |
Account coordinator is able to create sub-account, but failed to create new assoc. Log is below: [syrchin@master ~]$ sacctmgr add account test.0 parent=testproject Adding Account(s) test.0 Settings Description = Account Name Organization = Parent/Account Name Associations A = test.0 C = caba2 Settings Parent = testproject Would you like to commit changes? (You have 30 seconds to decide) (N/y): y [syrchin@master ~]$ sacctmgr show account withcoord Account Descr Org Coord Accounts ---------- -------------------- -------------------- -------------------- research + research accounts research root default root account root test.0 test.0 testproject syrchin testproje+ test project testproject syrchin [syrchin@master ~]$ sacctmgr show users User Def Acct Admin ---------- ---------- --------- use testproje+ None root root Administ+ syrchin testproje+ None yudin testproje+ None [syrchin@master ~]$ sacctmgr add user name=user account=test.0 Associations = U = user A = test.0 C = caba2 Non Default Settings Problem adding users: Access/permission denied User 'syrchin' created account test.0 (with parent=testproject). And then try to add 'user' to user this account (permission denied). Does this behavior specific for 17.02.09 (according to 5403 it is working in 17.11)? Is there any configuration to allow coordinator create assocs ?