hashicorp/nomad · error
missing node ID for evaluation
Error message
missing node ID for evaluation
What it means
The Node.Evaluate RPC failed argument validation: the request carried an empty NodeID, so the server has no node to force an evaluation for.
Source
Thrown at nomad/node_endpoint.go:1147
if done, err := n.srv.forward("Node.Evaluate", args, args, reply); done {
return err
}
n.srv.MeasureRPCRate("node", structs.RateMetricWrite, args)
if authErr != nil {
return structs.ErrPermissionDenied
}
defer metrics.MeasureSince([]string{"nomad", "client", "evaluate"}, time.Now())
// Check node write permissions
if aclObj, err := n.srv.ResolveACL(args); err != nil {
return err
} else if !aclObj.AllowNodeWrite() {
return structs.ErrPermissionDenied
}
// Verify the arguments
if args.NodeID == "" {
return fmt.Errorf("missing node ID for evaluation")
}
// Look for the node
snap, err := n.srv.fsm.State().Snapshot()
if err != nil {
return err
}
ws := memdb.NewWatchSet()
node, err := snap.NodeByID(ws, args.NodeID)
if err != nil {
return err
}
if node == nil {
return fmt.Errorf("node not found")
}
// Create the evaluation
evalIDs, evalIndex, err := n.createNodeEvals(node, node.ModifyIndex)View on GitHub (pinned to 482b49bf1a)
Solutions
- Populate NodeID in the EvaluateRequest before calling the endpoint
- Client-side, verify the node reference/flag used to build the request is not empty
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at nomad/node_endpoint.go:1147 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of hashicorp/nomad@482b49bf1a (2026-09-04).
Data as JSON: /api/errors/3c17dfcfe5e17ad5.
Report an issue: GitHub.