CI / test (push) Successful in 10m50s
Tried on the PoC: with a job on a lent node, the leader restarted and its first slurm.conf had no node in it (none had reported to it yet), so slurmctld dropped the node and the job ended in NODE_FAIL. The leader keeps slurm.conf's nodes and the controller's address in the store's cluster state (slurm-nodes); the next one starts from them and writes the same files until the nodes report again. With the store unread, the controller gets no files that leave a node out. A node is told nothing, rather than that it has no part, until its controller's address is known: no part stops slurmd, and its jobs with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>