hashicorp/nomad · error
invalid node pool: %v
Error message
invalid node pool: %v
What it means
NodeRegisterRequest.Validate failed the node pool name check at registration; the node's configured node_pool does not pass ValidateNodePoolName (allowed pattern is alphanumeric, hyphen, underscore, 1-128 chars).
Source
Thrown at nomad/structs/node.go:619
}
if n.Node.ID == "" {
return errors.New("missing node ID for client registration")
}
if n.Node.Datacenter == "" {
return errors.New("missing datacenter for client registration")
}
if n.Node.Name == "" {
return errors.New("missing node name for client registration")
}
if len(n.Node.Attributes) == 0 {
return errors.New("missing attributes for client registration")
}
if n.Node.SecretID == "" {
return errors.New("missing node secret ID for client registration")
}
if n.Node.NodePool != "" {
if err := ValidateNodePoolName(n.Node.NodePool); err != nil {
return fmt.Errorf("invalid node pool: %v", err)
}
if n.Node.NodePool == NodePoolAll {
return fmt.Errorf("node is not allowed to register in node pool %q", NodePoolAll)
}
}
return nil
}
// ShouldGenerateNodeIdentity compliments the functionality within
// AuthenticateNodeIdentityGenerator to determine whether a new node identity
// should be generated within the RPC handler.
func (n *NodeRegisterRequest) ShouldGenerateNodeIdentity(
authErr error,
now time.Time,
ttl time.Duration,
) bool {
View on GitHub (pinned to 482b49bf1a)
Solutions
- Fix the node pool name in the client's `node_pool` config
- Omit it to register into the `default` pool
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at nomad/structs/node.go:619 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/334866db147c4720.
Report an issue: GitHub.