Skip to content

Report sinfo and sacctmgr failures instead of an empty cluster - #48

Open
fedonman wants to merge 1 commit into
mainfrom
fixed/surface-sinfo-failures
Open

Report sinfo and sacctmgr failures instead of an empty cluster#48
fedonman wants to merge 1 commit into
mainfrom
fixed/surface-sinfo-failures

Conversation

@fedonman

@fedonman fedonman commented Sep 6, 2026

Copy link
Copy Markdown
Owner

list_partitions and list_nodes only checked that sinfo could be spawned, so a controller that was down gave an empty list that looked exactly like a small cluster, and check_slurm_available returned Ok whatever squeue --version exited with. The three list calls now return a Result carrying whatever the command printed, startup stops on a failing squeue, and a probe that fails is flashed rather than leaving the sidebar quietly empty. list_qos gets the same treatment, so a cluster with no accounting database is no longer indistinguishable from a sacctmgr that failed.

Closes #12

list_partitions and list_nodes only checked that sinfo could be spawned,
so a non-zero exit gave an empty list that looked like a small cluster,
and check_slurm_available returned Ok whatever squeue exited with.
list_qos did check the status but still returned an empty Vec, so the
caller could not tell a cluster with no accounting database from a
sacctmgr that failed. The three list calls now return a Result carrying
whatever the command printed, startup stops on a failing squeue, and a
failed probe is flashed instead of leaving the sidebar quietly empty.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: A down controller reads as a cluster with no partitions, nodes or QoS

1 participant