nomad node status: Check Nomad Client Nodes in CI
nomad node status lists the cluster client nodes with their status, eligibility, and drain state.
When a job will not place, the cause is often the nodes, not the jobspec. node status shows which clients are ready, draining, or ineligible.
What it does
nomad node status lists client nodes (or details one by ID) with their datacenter, status (ready, down, disconnected), scheduling eligibility (eligible or ineligible), and drain state. -self targets the local node and -allocs shows allocation counts per node.
Common usage
nomad node status
nomad node status -verbose
nomad node status -allocs
nomad node status <node-id>Options
| Flag | What it does |
|---|---|
| -self | Show status of the local node |
| -allocs | Show the number of allocations per node |
| -verbose | Full node IDs and additional fields |
| -json | Emit the node object(s) as JSON |
In CI
If nomad job run reports no eligible nodes, run node status to see whether nodes are down, ineligible, or draining. Make a node schedulable again with nomad node eligibility -enable -self after maintenance.
Common errors in CI
A node showing eligibility "ineligible" will never receive placements; re-enable it with nomad node eligibility. Status "down" means the client lost contact with the servers (heartbeat lost). "No node(s) with prefix ... found" means a wrong node ID; use -verbose to get the full IDs first.