-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
problem
Unable to launch a vm on vmware cluster
versions
ACS 4.22
vSphere Client version 8.0.3.00000
kvm ubuntu 24.0.4
The steps to reproduce the bug
-
Have a cloudstack zone with a vmware cluster and a KVM cluster
-
Make sure the systemvm's are running on kvm by setting the value "system.vm.default.hypervisor" to KVM
-
Register a ova template
-
Launch a vm on the vmware hypervisor
-
Vm fails to launch with the following exception
2025-12-23 10:51:46,865 INFO [c.c.h.v.u.VmwareHelper] (DirectAgent-11:[ctx-13625a0e, 192.168.55.162, job-2496/job-2497, cmd: CopyCommand]) (logid:09638309) [ignored]failed to get message for exception: Unable to access file /vmfs/volumes/7f631381-bb601b02/9fbc19108407304cb68734a287c50236/9fbc19108407304cb68734a287c50236-000001.vmdk since it is locked
2025-12-23 10:51:46,867 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-11:[ctx-13625a0e, 192.168.55.162, job-2496/job-2497, cmd: CopyCommand]) (logid:09638309) CopyCommand failed due to [Exception: java.lang.RuntimeException
Message: Unable to access file /vmfs/volumes/7f631381-bb601b02/9fbc19108407304cb68734a287c50236/9fbc19108407304cb68734a287c50236-000001.vmdk since it is locked
]. java.lang.RuntimeException: Unable to access file /vmfs/volumes/7f631381-bb601b02/9fbc19108407304cb68734a287c50236/9fbc19108407304cb68734a287c50236-000001.vmdk since it is locked
at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:428)
at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createFullClone(VirtualMachineMO.java:857)
at com.cloud.storage.resource.VmwareStorageProcessor.createVMFullClone(VmwareStorageProcessor.java:774)
at com.cloud.storage.resource.VmwareStorageProcessor.createVMAndFolderWithVMName(VmwareStorageProcessor.java:937)
at com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:860)
at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:107)
The issue doesn't occur if the system vm are running on kvm hypervisor or
If the ova Template is already present in the primary storage.
Previous related issue
What to do about it?
CloudStack should launch vm on vmware if the systemvm's are running
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done