hashicorp/nomad · error
max requested capacity (%s) less than or equal to min (%s)
Error message
max requested capacity (%s) less than or equal to min (%s)
What it means
Fires in expandVolume: the requested maximum capacity is smaller than the requested minimum (both humanized in the message); a valid expansion needs max >= min, indicating the claim's capacity fields were swapped or mistyped.
Source
Thrown at nomad/csi_endpoint.go:1327
)
// If requested capacity values are unset, skip everything.
if newMax == 0 && newMin == 0 {
logger.Debug("min and max values are zero")
return nil
}
// New values same as current, so nothing to do.
if vol.RequestedCapacityMax == newMax &&
vol.RequestedCapacityMin == newMin {
logger.Debug("requested capacity unchanged")
return nil
}
// If max is specified, it cannot be less than min or current capacity.
if newMax > 0 {
if newMax < newMin {
return fmt.Errorf("max requested capacity (%s) less than or equal to min (%s)",
humanize.Bytes(uint64(newMax)),
humanize.Bytes(uint64(newMin)))
}
if newMax < vol.Capacity {
return fmt.Errorf("max requested capacity (%s) less than or equal to current (%s)",
humanize.Bytes(uint64(newMax)),
humanize.Bytes(uint64(vol.Capacity)))
}
}
// Values are validated, so go ahead and update vol to commit to state,
// even if the external volume does not need expanding.
vol.RequestedCapacityMin = newMin
vol.RequestedCapacityMax = newMax
// Only expand if new min is greater than current capacity.
if newMin <= vol.Capacity {
return nilView on GitHub (pinned to 482b49bf1a)
Solutions
- Set min_requests_max greater than or equal to min_requests_min in the claim
- Re-issue the volume claim/expansion with corrected capacities
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at nomad/csi_endpoint.go:1327 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/8c76c41b1111f249.
Report an issue: GitHub.