Skip to content

Not able to deploy VM: Insufficient un-allocated capacity on StoragePool #14031

Closed
Closed
Not able to deploy VM: Insufficient un-allocated capacity on StoragePool#14031
Labels
component:orchestration
Milestone
4.22.2

Description

@mbertolina
mbertolina
opened on Sep 1, 2026

problem

When trying to deploy a VM from a template I get "Could not find suitable Deployment Destination for this VM under any clusters, returning." because of "Insufficient un-allocated capacity on: StoragePool..."

From template information:
Hypervisor: KVM
Format: qcow2
Template physical size: 20.81 GB
Template Size: 1912.00 GB

StoragePool:
Type: SharedMountPoint
Overprovisioning factor: 1
Disk Size (in GB): 4095.5 GB (x1.0)
0.05% Used
0.00% Allocated

Looking at the logs I see that the actual filesystem/storage usage reported here is only about 0.05%.

But later the logs says:

totalAllocatedSize: 2052994367488
allocated percentage: 0.9337067261132008

That's roughly 93.37% of the pool's capacity allocated/reserved according to CloudStack, not actual bytes currently consumed on the filesystem.

why CloudStack believes each pool has ~93.37% allocated ?
while the underlying storage reports only ~0.05% physically used ?

Does it use the template root disk size instead of qcow2 physical size?

2026-09-01 16:08:27,247 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f]) (logid:3edce1a3) Checking if  amount of resources of Type = 'primary_storage', tag = 'null' for Project Name = jsa in Domain Id = 5 is exceeded: Account Resource Limit = (-0.00 KB) -1, Current Account Resource Amount = (0 bytes) 0, Current Account Resource Reservation = (0 bytes) 0, Requested Resource Amount = (1.8672 TB) 2052994367488.
:
2026-09-01 16:08:27,249 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f]) (logid:3edce1a3) Checking if  domain resource limits of Type 'primary_storage' for Domain Id = ca57d812-2adc-40b1-b044-e329de0ac6f2 is exceeded: Domain Resource Limit = (-0.00 KB) -1, Current Domain Resource Amount = (0 bytes) 0, Current Resource Reservation = (0 bytes) 0, Requested Resource Amount = (1.8672 TB) 2052994367488.
:
2026-09-01 16:08:27,276 DEBUG [c.c.v.UserVmManagerImpl] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f]) (logid:3edce1a3) Root disk size specified is (1.8672 TB) 2052994367488 and Template root disk size is (1.8672 TB) 2052994367488. Both are equal so no need to override
:
2026-09-01 16:08:27,376 DEBUG [o.a.c.e.o.VolumeOrchestrator] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f, ctx-3b17f113]) (logid:3edce1a3) The specified root disk size of [(1.8672 TB) 2052994367488] bytes is smaller than the template. Using root disk size of [2052994367488] bytes for the volume [ROOT-66].
:
2026-09-01 16:08:27,394 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f, ctx-3b17f113]) (logid:3edce1a3) Updating resource Type = volume count for Account with id = 19 Operation = increasing Amount = 1
:
2026-09-01 16:08:27,398 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f, ctx-3b17f113]) (logid:3edce1a3) Updating resource Type = primary_storage count for Account with id = 19 Operation = increasing Amount = (1.8672 TB) 2052994367488
:
2026-09-01 16:08:27,417 DEBUG [c.c.v.ClusteredVirtualMachineManagerImpl] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f]) (logid:3edce1a3) Allocation completed for VM: VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}
:
2026-09-01 16:08:27,417 DEBUG [c.c.v.UserVmManagerImpl] (qtp2038105753-9093:[ctx-e0c445be, ctx-e5bd817f]) (logid:3edce1a3) Successfully allocated DB entry for VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}
:
:
2026-09-01 16:08:27,770 DEBUG [c.c.a.m.a.i.FirstFitRoutingAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710, FirstFitRoutingAllocator]) (logid:ccc59a67) Host Allocator returning 7 suitable hosts
2026-09-01 16:08:27,770 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Re-ordering hosts [Host {"id":17,"name":"wtc2b1fesx0501","type":"Routing","uuid":"bd2c3d29-2c73-482f-83d5-479ed18bbd0a"}, Host {"id":18,"name":"wtc2b1fesx0502","type":"Routing","uuid":"9ee31367-3f4b-496c-9f53-0f825ff65782"}, Host {"id":19,"name":"wtc2b1fesx0601","type":"Routing","uuid":"b344da4e-123f-4376-8e7d-ce6405647b59"}, Host {"id":20,"name":"wtc2b1fesx0301","type":"Routing","uuid":"4a208773-a87b-4757-b1f0-a0b777edbdb7"}, Host {"id":14,"name":"wtc2b1fesx0201","type":"Routing","uuid":"f300c7ab-ec0f-49c6-be68-e2167baa4ce0"}, Host {"id":15,"name":"wtc2b1fesx0202","type":"Routing","uuid":"7bbec373-a643-4dc7-ac8b-3dcc35381191"}, Host {"id":16,"name":"wtc2b1fesx0302","type":"Routing","uuid":"f9a87e6d-8afd-4837-bd06-7994f87e0868"}] by priorities {}
2026-09-01 16:08:27,771 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Hosts after re-ordering are: [Host {"id":17,"name":"wtc2b1fesx0501","type":"Routing","uuid":"bd2c3d29-2c73-482f-83d5-479ed18bbd0a"}, Host {"id":18,"name":"wtc2b1fesx0502","type":"Routing","uuid":"9ee31367-3f4b-496c-9f53-0f825ff65782"}, Host {"id":19,"name":"wtc2b1fesx0601","type":"Routing","uuid":"b344da4e-123f-4376-8e7d-ce6405647b59"}, Host {"id":20,"name":"wtc2b1fesx0301","type":"Routing","uuid":"4a208773-a87b-4757-b1f0-a0b777edbdb7"}, Host {"id":14,"name":"wtc2b1fesx0201","type":"Routing","uuid":"f300c7ab-ec0f-49c6-be68-e2167baa4ce0"}, Host {"id":15,"name":"wtc2b1fesx0202","type":"Routing","uuid":"7bbec373-a643-4dc7-ac8b-3dcc35381191"}, Host {"id":16,"name":"wtc2b1fesx0302","type":"Routing","uuid":"f9a87e6d-8afd-4837-bd06-7994f87e0868"}]
:
:
2026-09-01 16:08:27,773 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Checking suitable pools for volume [Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"}, ROOT] of VM [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}].
:
2026-09-01 16:08:27,776 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Calling StoragePoolAllocators to find suitable pools to allocate volume [Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"}] necessary to deploy VM [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}].
2026-09-01 16:08:27,776 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Trying to find suitable pools to allocate volume [Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"}] necessary to deploy VM [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}], using StoragePoolAllocator: [LocalStoragePoolAllocator].
2026-09-01 16:08:27,777 TRACE [o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) [LocalStoragePoolAllocator] is looking for storage pools that match the VM's disk profile [DskChr[ROOT|2052994367488|]], virtual machine profile [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}] and deployment plan [{"_clusterId":2,"_dcId":1,"_physicalNetworkId":null,"_podId":1,"_poolId":null,"migrationPlan":false}]. Returning up to [-1] and bypassStorageTypeCheck [false].
2026-09-01 16:08:27,777 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) LocalStoragePoolAllocator is returning null since the disk profile does not use local storage and bypassStorageTypeCheck is false.
2026-09-01 16:08:27,777 INFO  [o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) There are no pools to reorder.
2026-09-01 16:08:27,777 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Trying to find suitable pools to allocate volume [Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"}] necessary to deploy VM [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}], using StoragePoolAllocator: [ClusterScopeStoragePoolAllocator].
2026-09-01 16:08:27,777 TRACE [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) [ClusterScopeStoragePoolAllocator] is looking for storage pools that match the VM's disk profile [DskChr[ROOT|2052994367488|]], virtual machine profile [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}] and deployment plan [{"_clusterId":2,"_dcId":1,"_physicalNetworkId":null,"_podId":1,"_poolId":null,"migrationPlan":false}]. Returning up to [-1] and bypassStorageTypeCheck [false].
2026-09-01 16:08:27,777 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Looking for pools in dc [1], pod [1], cluster [2], and having tags [[rp01]]. Disabled pools will be ignored.
:
2026-09-01 16:08:27,797 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Found pools [[StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}, StoragePool {"id":39,"name":"wtc2b1f_ds_rp01_02","poolType":"SharedMountPoint","uuid":"7c394014-e795-453a-bf4e-46c008779b41"}, StoragePool {"id":40,"name":"wtc2b1f_ds_rp01_03","poolType":"SharedMountPoint","uuid":"08e1cd19-3cf1-4bec-baf2-a5147688741e"}, StoragePool {"id":41,"name":"wtc2b1f_ds_rp01_04","poolType":"SharedMountPoint","uuid":"af8d1ec2-9d18-4c35-9c6f-63b4f3c29173"}, StoragePool {"id":42,"name":"wtc2b1f_ds_rp01_05","poolType":"SharedMountPoint","uuid":"1de9d65a-7604-4094-8b3e-870daad6d7e0"}]] that match with tags [[rp01]].
:
2026-09-01 16:08:27,799 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Checking if storage pool [StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}] is suitable to disk [DskChr[ROOT|2052994367488|]].
:
2026-09-01 16:08:27,801 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Volume [Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"}] is not allocated to any pool. Cannot check compatibility with pool [StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}].
2026-09-01 16:08:27,801 INFO  [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Storage pool StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"} does not supply IOPS capacity, assuming enough capacity
:
2026-09-01 16:08:27,803 TRACE [o.a.c.f.c.ConfigKey] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Global value for config (pool.storage.capacity.disablethreshold): 0.85
:
2026-09-01 16:08:27,803 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Checking pool StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"} for storage, totalSize: 4397514358784, usedBytes: 2170425344, usedPct: 4.935573069055687E-4, disable threshold: 0.85
2026-09-01 16:08:27,803 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Destination pool: StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}
:
2026-09-01 16:08:27,814 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Pool ID for the volume Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"} is null
:
2026-09-01 16:08:27,817 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Found storage pool StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"} of type SharedMountPoint with overprovisioning factor 1
2026-09-01 16:08:27,817 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Total over provisioned capacity calculated is 1 * (3.9995 TB) 4397514358784
2026-09-01 16:08:27,817 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Total capacity of the pool StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"} is (3.9995 TB) 4397514358784
:
:
2026-09-01 16:08:27,820 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Checking pool: StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"} for storage allocation , maxSize : (3.9995 TB) 4397514358784, totalAllocatedSize : (1.8672 TB) 2052994367488, askingSize : (1.8672 TB) 2052994367488, allocated disable threshold: 0.85
2026-09-01 16:08:27,820 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Insufficient un-allocated capacity on: StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"} for storage allocation since its allocated percentage: 0.9337067261132008 has crossed the allocated pool.storage.allocated.capacity.disablethreshold: 0.85
2026-09-01 16:08:27,820 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Adding storage pool [StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"}] to avoid set during allocation of disk [DskChr[ROOT|2052994367488|]].
:
:
:
2026-09-01 16:08:27,887 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Checking pool: StoragePool {"id":42,"name":"wtc2b1f_ds_rp01_05","poolType":"SharedMountPoint","uuid":"1de9d65a-7604-4094-8b3e-870daad6d7e0"} for storage allocation , maxSize : (3.9995 TB) 4397514358784, totalAllocatedSize : (1.8672 TB) 2052994367488, askingSize : (1.8672 TB) 2052994367488, allocated disable threshold: 0.85
2026-09-01 16:08:27,887 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Insufficient un-allocated capacity on: StoragePool {"id":42,"name":"wtc2b1f_ds_rp01_05","poolType":"SharedMountPoint","uuid":"1de9d65a-7604-4094-8b3e-870daad6d7e0"} for storage allocation since its allocated percentage: 0.9337067261132008 has crossed the allocated pool.storage.allocated.capacity.disablethreshold: 0.85
2026-09-01 16:08:27,887 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Adding storage pool [StoragePool {"id":42,"name":"wtc2b1f_ds_rp01_05","poolType":"SharedMountPoint","uuid":"1de9d65a-7604-4094-8b3e-870daad6d7e0"}] to avoid set during allocation of disk [DskChr[ROOT|2052994367488|]].
2026-09-01 16:08:27,887 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) [ClusterScopeStoragePoolAllocator] is returning [0] suitable storage pools [[]].
2026-09-01 16:08:27,887 INFO  [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Reordering [0] pools
:
2026-09-01 16:08:27,887 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Trying to find suitable pools to allocate volume [Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"}] necessary to deploy VM [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}], using StoragePoolAllocator: [ZoneWideStoragePoolAllocator].
:
2026-09-01 16:08:27,891 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Could not find any zone wide storage pool that matched with any of the following tags [[rp01]].
:
2026-09-01 16:08:27,892 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) [ZoneWideStoragePoolAllocator] is returning [0] suitable storage pools [[]].
:
2026-09-01 16:08:27,892 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) No suitable pools found for volume [Volume {"id":85,"instanceId":66,"name":"ROOT-66","uuid":"0ae87c7e-c412-41a4-932e-715864c18a3a","volumeType":"ROOT"}] used by VM [VM instance {"id":66,"instanceName":"i-19-66-VM","state":"Stopped","type":"User","uuid":"de530012-9244-462d-ac72-73cd28bd1af5"}] under cluster: [2].
2026-09-01 16:08:27,892 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) No suitable pools found
2026-09-01 16:08:27,892 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) No suitable storagePools found under this Cluster: Cluster {id: "2", name: "rp01", uuid: "f27cce5c-a1f6-49d0-a556-8c21a8816183"}
:
2026-09-01 16:08:27,893 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Could not find suitable Deployment Destination for this VM under any clusters, returning.
:
2026-09-01 16:08:27,894 DEBUG [c.c.d.FirstFitPlanner] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Searching all possible resources under this Zone: Zone {"id": "1", "name": "wtc2b1f_zone", "uuid": "2a08dda1-e760-47fb-828d-a9b07be9313c"}

versions

Cloudstack: 4.22.1.0
KVM host: rhel9.8
Primary storage: Shared storage on GFS2

The steps to reproduce the bug

...

What to do about it?

No response

Activity

  1. mbertolina
    added
    bug
    on Sep 1, 2026

  2. weizhouapache commented on Sep 1, 2026

    @weizhouapache
    weizhouapache
    on Sep 1, 2026
    Member

    Overprovisioning factor: 1

    increase this and retry

  3. mbertolina commented on Sep 1, 2026

    @mbertolina
    mbertolina
    on Sep 1, 2026
    Author

    Although changing this parameter may cause the VM to deploy, it is not the expected result, and besides that, I want the calculated space not to exceed the size of the primary storage disk (x1.0).

    In think the problem is not the overprovisioning factor, it is how the available space is calculated, when allocating 1.9T root disk from template (details above) on an empty 4 TB primary storage (reporting: Disk Size (in GB): 4095.5 GB (x1.0), 0.05% Used,
    0.00% Allocated)

    Why: totalAllocatedSize : (1.8672 TB) 2052994367488 ? is it using "template size" for this calculation instead of the physical size of the qcow2 file which is "Template physical size: 20.81 GB"?

    2026-09-01 16:08:27,820 DEBUG [c.c.s.StorageManagerImpl] (API-Job-Executor-70:[ctx-e0d2082a, job-531, ctx-4c31b710]) (logid:ccc59a67) Checking pool: StoragePool {"id":38,"name":"wtc2b1f_ds_rp01_01","poolType":"SharedMountPoint","uuid":"b9dec035-9ef1-496f-9285-11eb50dad305"} for storage allocation , maxSize : (3.9995 TB) 4397514358784, totalAllocatedSize : (1.8672 TB) 2052994367488, askingSize : (1.8672 TB) 2052994367488, allocated disable threshold: 0.85

  4. mbertolina commented on Sep 2, 2026

    @mbertolina
    mbertolina
    on Sep 2, 2026
    Author

    As a workaround, After setting overprovisioning factor to 2 I was able to deploy the VM.

    Image

  5. weizhouapache commented on Sep 2, 2026

    @weizhouapache
    weizhouapache
    on Sep 2, 2026
    Member

    Although changing this parameter may cause the VM to deploy, it is not the expected result, and besides that, I want the calculated space not to exceed the size of the primary storage disk (x1.0).

    @mbertolina
    I am not sure why you want to enforce this. In most virtualized environments, virtual disks are thin-provisioned, so the actual used space can be much smaller than the virtual disk size.

  6. DaanHoogland
    added this to the 4.22.2 milestone on Sep 2, 2026
  7. DaanHoogland
    added
    component:orchestration
    and removed
    bug
    on Sep 2, 2026
  8. DaanHoogland
    added the
    Bug
    issue type on Sep 2, 2026
  9. DaanHoogland
    added this to Apache CloudStack BugFest - Issueson Sep 2, 2026

  10. mbertolina commented on Sep 2, 2026

    @mbertolina
    mbertolina
    on Sep 2, 2026
    Author

    I tested with a thin disk service offering and Overprovisioning factor=1 on primary storage and got the same error when allocating the space for the VM

  11. weizhouapache commented on Sep 3, 2026

    @weizhouapache
    weizhouapache
    on Sep 3, 2026
    Member

    I tested with a thin disk service offering and Overprovisioning factor=1 on primary storage and got the same error when allocating the space for the VM

    @mbertolina
    Let me give you an example:

    • Create a 100 GB ROOT disk. The actual physical usage is only 5 GB (for the operating system).
    • Create a 100 GB DATA disk. The actual physical usage is 0 GB because it is empty.

    In this case, the total allocated size is 200 GB, but only 5 GB is actually used on the physical storage pool.

    If the storage pool size is 200 GB:

    • With an overprovisioning factor of 1, you cannot create any new volumes because the total allocated capacity has already reached 200 GB (200 × 1), even though only 5 GB is physically used.
    • With an overprovisioning factor of 5, the total allocated capacity is 1,000 GB (200 × 5), so you can still create several volumes. However, there is a risk that the virtual disks eventually consume their full 100 GB each, which could result in the physical storage pool becoming full.

    This is the trade-off with overprovisioning: a lower factor provides more protection against the storage pool becoming full, but may leave physical capacity underutilized. A higher factor allows you to make better use of the physical storage, but increases the risk of running out of physical space if the volumes actually consume their allocated capacity.

  12. DaanHoogland commented on Sep 3, 2026

    @DaanHoogland
    DaanHoogland
    on Sep 3, 2026
    Contributor

    I tested with a thin disk service offering and Overprovisioning factor=1 on primary storage and got the same error when allocating the space for the VM

    @mbertolina this sounds like a way to hit the limit sooner, rather than later. If thin provisioning, it will not occupy the space completely from the start, but it will mark it as allocated. thin provisioning and overprovisioning work together to help you make good use of your disk space. If say half your disks are thin provisioned and they take about 10% of the space you need and the other half are thick provisioned, you would want 0.5*0.1 + 0.5 times the physical space to be able to allocate all. You would then use 5+0.5 times the space you actually have to be allocatable. Rounding down for safety of course. Also keep in mind life-spans of VMs, are they expected to grow to their full size during their life-time or will they be recycled when half way through their space. I wrote this while @weizhouapache replied. We are saying basically the same thing but in slightly different ways. Please ask more questions or if you understand help us improve the documentation at https://github.com/apache/cloudstack-documentation

  13. DaanHoogland
    removed the
    Bug
    issue type on Sep 3, 2026
  14. apache
    locked and limited conversation to collaborators on Sep 3, 2026
  15. DaanHoogland
    converted this issue into a discussion #14045 on Sep 3, 2026
  16. github-project-automation
    moved this to Done in Apache CloudStack BugFest - Issueson Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:orchestration

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions