GitHub user prashanthr2 added a comment to the discussion: How to debug VM
deployment issues (capacity issues?)
@bradh352 I see below in the logs
2025-12-04 14:33:19,426 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator]
(Work-Job-Executor-6:[ctx-8a912d50, job-21766/job-21769, ctx-77b2d201])
(logid:de988890) Using volume allocation algorithm random to reorder pools.
2025-12-04 14:33:19,426 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-6:[ctx-8a912d50, job-21766/job-21769, ctx-77b2d201])
(logid:de988890) Trying to find suitable pools to allocate volume [Volume
{"id":1701,"instanceId":661,"name":"ROOT-661","uuid":"09fa0cd6-5db0-4029-aa23-45e5d285574a","volumeType":"ROOT"}]
necessary to deploy VM [VM instance
{"id":661,"instanceName":"r-661-VM","state":"Starting","type":"DomainRouter","uuid":"2af967de-e5a8-4ded-8e42-cc3c9923daac"}],
using StoragePoolAllocator: [ZoneWideStoragePoolAllocator].
2025-12-04 14:33:19,428 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
(Work-Job-Executor-6:[ctx-8a912d50, job-21766/job-21769, ctx-77b2d201])
(logid:de988890) Checking if storage pool [StoragePool
{"id":1,"name":"vm-images","poolType":"RBD","uuid":"824b8d90-5fd8-3d34-9008-e982e8a4196c"}]
is suitable to disk [DskChr[ROOT|5242880000|]].
_**2025-12-04 14:33:19,428 DEBUG [c.c.s.StorageManagerImpl]
(Work-Job-Executor-6:[ctx-8a912d50, job-21766/job-21769, ctx-77b2d201])
(logid:de988890) Cannot check compatibility of pool [StoragePool
{"id":1,"name":"vm-images","poolType":"RBD","uuid":"824b8d90-5fd8-3d34-9008-e982e8a4196c"}]
because volume [Volume
{"id":1701,"instanceId":661,"name":"ROOT-661","uuid":"09fa0cd6-5db0-4029-aa23-45e5d285574a","volumeType":"ROOT"}]
is not in [Ready] state.**_
2025-12-04 14:33:19,428 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator]
(Work-Job-Executor-6:[ctx-8a912d50, job-21766/job-21769, ctx-77b2d201])
(logid:de988890) Pool [StoragePool
{"id":1,"name":"vm-images","poolType":"RBD","uuid":"824b8d90-5fd8-3d34-9008-e982e8a4196c"}]
is not compatible with volume [Volume
{"id":1701,"instanceId":661,"name":"ROOT-661","uuid":"09fa0cd6-5db0-4029-aa23-45e5d285574a","volumeType":"ROOT"}],
skipping it.
What is the state of the volume associated with the VR? r-661-VM. The
deployment/Start of the VR is failing causing the VM starts to fail.. Can you
try to do network restart with cleanup=true
GitHub link:
https://github.com/apache/cloudstack/discussions/12192#discussioncomment-15162245
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
