Error: "storage containers rejected because: Threshold would be violated" occurs during creation of a named disk
Article ID: 419736
Updated On:
Products
Issue/Introduction
- Creation of a named disk or vm fails.
- The resulting error displays messages similar to:
The operation failed because no suitable resource was found. Out of 1 candidate hubs: 1 hubs eliminated because: No valid storage containers found for NamedDisk "<disk-uuid>". All # available storage containers were filtered out as being invalid. Rejected hubs: resgroup-<id>Storage containers were rejected for the following reasons: 1 storage containers rejected because: Threshold would be violated. Rejected storage containers: <datastore-name>
Environment
VMware Cloud Director 10.6.1
Cause
You can configure low disk space thresholds (red/yellow thresholds) on storage containers in Cloud Director. This issue occurs if the disk is being deployed to a storage container/datastore which has breached the configured storage thresholds. The Cloud Director placement engine stops placing objects on the datastore when this occurs.
Resolution
To resolve the issue:
- Inspect the current storage capacity utilization on the storage container/datastore(s).
- Inspect the configured red/yellow thresholds in Cloud Director.
Configure Low Disk Space Thresholds for a Provider Virtual Data Center Storage Container:
View the Datastores and Datastore Clusters on a Provider Virtual Data Center in Your VMware Cloud Director
Based on your inspection of the environment, take appropriate action to either make available additional capacity on the storage container/datastore(s) or alternatively modify the red/yellow threshold settings if appropriate.
Additional Information
Feedback
