DaanHoogland commented on issue #11052:
URL: https://github.com/apache/cloudstack/issues/11052#issuecomment-2995426326
@nimbustech-lab, I don’t think the problemetic log entry will contain the VM
name. Grep for can you grep for i-4-619-VM will not yield the issue. Can you
grep job-2149 in that file, and look for errors and excpetions in that output ?
looking at the lines
```
2025-06-20 02:48:14,427 DEBUG [c.c.s.r.StorageSubsystemCommandHandlerBase]
(DirectAgent-345:ctx-11d49002 192.168.80.81, job-2149/job-2150, cmd:
CopyCommand) (logid:9556019e) Executing command CopyCommand:
[{"srcTO":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"5ac6b8c4a7af3e3fbf2fb321fffd9dd7","uuid":"a1905274-90d1-4c9e-bbf1-6067fc93ffda","id":221,"format":"OVA","accountId":4,"hvm":true,"displayText":"This
is the template for Windows Server 2022 with custom (unconstrained)
offering.","imageDataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"c651d575-bfbc-401e-bb0c-b23963a38df9","name":"ds-cloudstack","id":4,"poolType":"VMFS","host":"VMFS
datastore: datastore-16","path":"datastore-16","port":0,"url":"VMFS://VMFS
datastore:
datastore-16/datastore-16/?ROLE=Primary&STOREUUID=c651d575-bfbc-401e-bb0c-b23963a38df9","isManaged":false}},"name":"221-4-cdb53111-8212-38a5-91ec-2bece31fe4b9","size":37580963840,"hypervisorType":"VMware","bootable":false,"u
niqueName":"221-4-cdb53111-8212-38a5-91ec-2bece31fe4b9","directDownload":false,"deployAsIs":false,"followRedirects":false}},"destTO":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"3fe7354e-5cad-4616-a1a2-996ff4486e2e","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"c651d575-bfbc-401e-bb0c-b23963a38df9","name":"ds-cloudstack","id":4,"poolType":"VMFS","host":"VMFS
datastore: datastore-16","path":"datastore-16","port":0,"url":"VMFS://VMFS
datastore:
datastore-16/datastore-16/?ROLE=Primary&STOREUUID=c651d575-bfbc-401e-bb0c-b23963a38df9","fullCloneFlag":true,"diskProvisioningStrictnessFlag":false,"isManaged":false}},"name":"ROOT-619","size":37580963840,"volumeId":614,"vmName":"i-4-619-VM","accountId":4,"format":"OVA","provisioningType":"FAT","poolId":4,"id":614,"deviceId":0,"cacheMode":"WRITETHROUGH","hypervisorType":"VMware","directDownload":false,"deployAsIs":false,"followRedirects":false}},"executeInSequence":true,"options":
{},"options2":{},"wait":0,"bypassHostMaintenance":false}].
2025-06-20 02:48:14,556 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-29:ctx-94f5ba93 job-2149/job-2150 ctx-01b8dfa1)
(logid:9556019e) Cleaning up resources for the vm VM instance
{"id":619,"instanceName":"i-4-619-VM","type":"User","uuid":"cd1d3dd3-8474-4b1c-80b3-a2d9d34e3367"}
in Starting state
```
it is probably somewhere between 02:48:14,427 and 02:48:14,556 that the
allocator-choosen storage pool turns out to be full or some other problem with
it occurs? It may also be a problem with the source file, though. I can’t tell
yet.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
