Getting Node Details

From the Nodes page (see Listing Nodes), click any row to open a Node details dialog showing:

• Node Information: ID, hostname, CPU, and memory, plus cluster when the node reports a cluster ID.
• Status: what Fuzzball has observed about the node, and when it last reported.
• Holds: what has been asked of the node – each hold’s effect, who placed it, and the reason recorded on it. Shown only when the node carries any.
• Attributed job failures: how many jobs stopped responding on this node, and when the last one did. Shown only when there are any.
• Resource Summary: total, allocated, and available cores and memory.
• Device Summary: per-device counts (total, requested, and available) when consumable devices are present on the node.
• Annotations: key/value annotations set on the node (for example, nvidia.com/gpu.model), useful for identifying what to target with a workflow’s resource requirements. Shown only when the node has any.
• Running Jobs: each running job’s ID, name, workflow ID, requested cores and memory, requested devices, and start time. Click a Job ID to jump to that job within its workflow.

Get detailed information about a specific node by providing its node ID:

$ fuzzball node show <node-id>

Example:

$ fuzzball node show 172.21.0.6/7333
ID:        172.21.0.6/7333
Hostname:  substrate-localnode-1
CPU:       cpu/arm64
Substrate: v2.7.0
Cluster:   local-dev
Status:    Ready
Reported:  2026-09-17T14:05:00Z
Holds: 1
  7f3c1a90-2b11-4e6d-9a7f-2f0c5d8e1b42  cordon  admin  "failing disk, replacing Friday"
    since 2026-09-14T14:02:11Z
Resources:
  Cores:     20 total (1 allocated, 19 available)
  Memory:    127.9 GB total (1.0 GB allocated, 126.9 GB available)
  nvidia.com/gpu:  1 total (0 requested, 1 available)

JOB ID                               | JOB NAME        | REQUESTED CORES | REQUESTED MEMORY (GB) | REQUESTED DEVICES
fab5985c-3157-5e6c-b60b-f2fd8e17fefd   data-processing   2                 4.0                     nvidia.com/gpu:1
e3211b77-117a-54ce-a2d9-420b4c673416   Hidden Job        1                 1.0                     None

The output includes:

• ID: Node identifier
• Hostname: Network hostname
• CPU: CPU model name or architecture
• Substrate: The fuzzball-substrate version running on the node, as reported by substrate itself. Only shown when the node reports it (older substrate versions omit it).
• Cluster: Resolved name of the Fuzzball cluster this node belongs to, or the raw cluster_id if the name cannot be resolved. Only shown when cluster_id is present — most visible when connected to a Federate cluster where nodes span multiple underlying Orchestrate clusters.

Each hold records something that has been asked of the node: its id, the effect (cordon, evict or deprovision), who placed it, an optional reason, and when it was placed. The section is omitted when the node carries no holds.

Holds are separate from status because they answer a different question. Status reports what Fuzzball has observed about the node; a hold reports what somebody decided about it. A node reading Ready with a cordon hold is not a contradiction – the hardware is fine and no new work will be placed there.

Only an administrator can place or release a hold. See Node Cordoning and Uncordoning.

• Status: What Fuzzball has observed about the node – Ready, Not Ready, Offline, or Unknown before its first report. A cordon is a hold, not a status; see Holds
• Reported: When the node last sent a health report. A node that has never reported says so rather than showing a zero timestamp.
• Attributed job failures: How many jobs stopped responding on this node, and when the last one did. Omitted when there are none.

For what each status means and how a silent node is detected, see Node Health Monitoring.

• Total: Capacity of the node
• Allocated: Currently in use by running jobs
• Available: Free capacity for new jobs

Consumable resources are tracked per device type:

• Total Count: Number of devices installed on the node
• Requested Count: Devices currently requested by jobs
• Available Count: Devices remaining that are not requested by jobs

For each job that is currently running on the node:

• JOB ID: Unique identifier for the job
• JOB NAME: Job name from the workflow definition
• REQUESTED CORES: CPU cores requested by the job
• REQUESTED MEMORY (GB): Memory requested by the job
• REQUESTED DEVICES: Consumable devices requested by the job

Jobs shown are workflow stages currently executing on this node. If you don’t have permission to view the corresponding workflow, the job will appear as “Hidden Job” with only the job ID visible.

By default the command prints the human-readable summary shown above. For programmatic access or scripting, request structured output with -o json or -o yaml:

$ fuzzball node show <node-id> -o json

The structured output includes additional low-level fields not shown in the default view, suitable for parsing with tools like jq or yq.