We occasionally need to rename a SLURM account (account named after person who has left, typo, whatever) and it's currently not possible to do this. Jess Arrington requested that we add an enhancement request to track the fact that a site wanted this option. We know you can destroy/create, but the job accounting data is then lost, and tracking usage is very important for our site, and probably is for most sites (funding reasons, etc.).
Was Tim Wickberg who asked us to put this in, to be more accurate.
Is this still active? I would like to +1 this. We delegate management of their groups to our PIs and we'll have to disable the ability for them to rename groups without this feature. Thanks, Todd
I guess as active as it ever was, which is to say "not very." I agree, it's an ongoing problem, and to me it doesn't seem impossible to fix, but I'm told there are things that complicate it that are not immediately obvious. More votes helps, I think.
The "Unassigned Developer" and lack of a target release are our hints that this isn't an active enhancement, and is simply an outstanding feature request. The rename, as Ryan notes, would be somewhat complicated with our current accounting database structure, especially in how to flag the transition. At this point I don't have any plan to address this.
Please +1 for this. I guess it's a design flaw that the account name is a primary key, ON UPDATE CASCADE should work at the database level? Then just updating the name should propagate it to the referring tables? Thank you
