All, I am seeing what looks like the same issue as https://bugs.schedmd.com/show_bug.cgi?id=2119
Where, slurmctld is not picking up new accounts unless it is restarted. I have 4 clusters (non-federated), all using the same slurmdbd When I added an association for user name=me cluster=DevOps account=Project1 and then tried to start a job, I kept getting an error: *srun: error: Unable to allocate resources: Invalid account or account/partition combination specified* Then I restarted slurmctld on DevOps master and my job ran fine. Is there some slurmdbd caching going on by slurmctld? This is an issue in a production environment. We don't want to have to restart all the slurmctld daemons anytime there is a change to any associations. That could get painful Brian Andrus
