Bill,
This patch appears to be a good idea. I modified it a bit to handle if
jobs were running on the associations and also moved the output to right
above the commit line. It also would remove the user if you just
removed the user from just one cluster and you have other associations
on other clusters. Let me know if you see any issues from your end, the
submitted patch seems to cover all these bases.
The patch
(https://github.com/SchedMD/slurm/commit/0fe8e29f2d99d889a13c0c69abff97e9a1631aa1)
will be in the next 2.4 release. In the mean time, anyone wanting to
see if there are "orphan" users in the system can use 'sacctmgr list
problems' which should list them to be removed.
Danny
On 01/13/12 10:47, bill.bro...@bull.com wrote:
A user discovered that it is possible to leave an orphan "user" in the
slurm db when the last "user" "account" association is deleted. This
inconsistency prevents an automatic update tool from detecting that
these orphan users are still present in the db. Since slurm doesn't
allow creation of orphan users, it makes sense to remove users who are
no longer associated with any account. The attached patch resolves
this issue.
Best Regards,
Bill
