-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
problem
After upgrading VMware to 8.0.3, i got this error during every FIRST deployment of VM from new template. Next deployments from that template are fine, but this error repeats multiple times.
This first VM is usually deployed successfully regardless of these errors, but sometimes it is not.
I can see the same errors in management-server.log as well as in vCenter.
2025-11-09 13:50:36,318 INFO [c.c.h.v.u.VmwareHelper] (DirectAgent-34:[ctx-e96ea891, exp070103a.infra.rpc.datacentrum.sk, job-522/job-524, cmd: CopyCommand]) (logid:6403181a) [ignored]failed to get message for exception: Unable to access file /vmfs/volumes/686bd05a-e4a7d1d3-28cd-62e53b800068/fb0a3c60dd74350281c0e7de141ae92b/fb0a3c60dd74350281c0e7de141ae92b-000001.vmdk since it is locked
2025-11-09 13:50:36,318 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-34:[ctx-e96ea891, exp070103a.infra.rpc.datacentrum.sk, job-522/job-524, cmd: CopyCommand]) (logid:6403181a) CopyCommand failed due to [Exception: java.lang.RuntimeException
Message: Unable to access file /vmfs/volumes/686bd05a-e4a7d1d3-28cd-62e53b800068/fb0a3c60dd74350281c0e7de141ae92b/fb0a3c60dd74350281c0e7de141ae92b-000001.vmdk since it is locked
]. java.lang.RuntimeException: Unable to access file /vmfs/volumes/686bd05a-e4a7d1d3-28cd-62e53b800068/fb0a3c60dd74350281c0e7de141ae92b/fb0a3c60dd74350281c0e7de141ae92b-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:773)
at com.cloud.storage.resource.VmwareStorageProcessor.createVMAndFolderWithVMName(VmwareStorageProcessor.java:936)
at com.cloud.storage.resource.VmwareStorageProcessor.cloneVolumeFromBaseTemplate(VmwareStorageProcessor.java:859)
at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:107)
at com.cloud.storage.resource.VmwareStorageSubsystemCommandHandler.execute(VmwareStorageSubsystemCommandHandler.java:209)
at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:65)
at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:592)
at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:306)
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
versions
ACS: 4.21
VMware vCenter 8.0.3
Vmware ESXi 8.0.3
Primary storage is VMFS datastores on SAN storage
The steps to reproduce the bug
- Create new template - for example Ubuntu 24.04
- Deploy new VM in ACS from this template
i had this error consistently in all my production and testing environments.
What to do about it?
It is eventually working, but i presume it is not very good to see multiple such an errors and deployment of first VM is taking very long time