vCLS deployment keep on failing with the error "The task was cancelled by a user"
search cancel

vCLS deployment keep on failing with the error "The task was cancelled by a user"

book

Article ID: 345293

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

  • vCLS VMs deployment is in a loop
  • Deployment OVF template task says, "The task was canceled by a user."
  • Disabled vCLS on Cluster via Retreat Mode does not fix the issue
  • Restarting EAM service on vCenter server does not fix the issue
  • In /var/log/vmware/eam/eam.log  we see entries similar to the following
YYYY:MM:DD:hh:mm:ss: Z INFO | vim-async-2 | AbstractErrorHandler.java | 41 | Error, leading to followup action, during Virtual Machine deletion.
        com.vmware.eam.exception.AlreadyInRequiredState: VM already destroyed
        at com.vmware.eam.vim.vm.impl.VirtualMachine.destroyExcTransform(VirtualMachine.java:380) ~[eam-server.jar:?]
        at com.vmware.eam.vim.task.impl.VimTask.processCompleted(VimTask.java:99) ~[eam-server.jar:?]
        at com.vmware.eam.vim.task.impl.VimTask.lambda$triggerPullResult$1(VimTask.java:75) ~[eam-server.jar:?]
        at com.vmware.eam.transform.impl.TransformationWrapper.transform(TransformationWrapper.java:54) [eam-server.jar:?]
        at com.vmware.eam.async.remote.Completion.onResult(Completion.java:66) [eam-server.jar:?]
        at com.vmware.eam.vmomi.async.FutureAdapter.set(FutureAdapter.java:71) [eam-server.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$ClientFutureAdapter.set(MethodInvocationHandlerImpl.java:721) [vlsi-client.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$RetryingFuture.set(MethodInvocationHandlerImpl.java:528) [vlsi-client.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:236) [vlsi-client.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:271) [vlsi-client.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.invokeWithinScope(HttpExchange.java:54) [vlsi-client.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:24) [vlsi-client.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.run(HttpExchangeBase.java:57) [vlsi-client.jar:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_351]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_351]
        at java.lang.Thread.run(Thread.java:750) [?:1.8.0_351]
        Caused by: com.vmware.vim.binding.vmodl.fault.ManagedObjectNotFound: The object 'vim.VirtualMachine:vm-XXXXXX' has already been deleted or has not been completely created
        at sun.reflect.GeneratedConstructorAccessor138.newInstance(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_351]
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_351]
        at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_351]
        at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) ~[vlsi-core.jar:?]
        at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25) ~[vlsi-core.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30) ~[vlsi-core.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.StackContextFactory.newContext(StackContextFactory.java:113) ~[vlsi-core.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.FaultStackContext.getNestedContext(FaultStackContext.java:86) ~[vlsi-core.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallContext.beginElement(UnmarshallerImpl.java:365) ~[vlsi-core.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallContext.parse(UnmarshallerImpl.java:274) ~[vlsi-core.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallContext.parse(UnmarshallerImpl.java:227) ~[vlsi-core.jar:?]
  • In the /var/log/vmware/vpxd/vpxd.log, we see entries similar to the following
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=vpxLro opID=53d75ece-01] [VpxLRO] -- BEGIN task-1510009 -- Resources -- ResourcePool.ImportVAppLRO --
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=vpxLro opID=53d75ece-01-01] [VpxLRO] -- BEGIN lro-755 --  -- ResourcePool.ImportVAppLRO --
YYYY:MM:DD:hh:mm:ss Z warning vpxd[31648] [Originator@6876 sub=VmProv opID=53d75ece-01-01] Unable to lookup ds for disk
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=vpxLro opID=53d75ece-01-01-01] [VpxLRO] -- BEGIN lro-756 --  -- VmprovWorkflow --
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=pbm opID=53d75ece-01-01-01] No datastore for disk -101 in config, filePath ds:///vmfs/volumes/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXX/
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=VmCheck opID=53d75ece-01-01-01] CompatCheck results: (vim.vm.check.Result) [
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=VmProv opID=53d75ece-01-01-01] Creating VM with spec (vim.vm.ConfigSpec) {
YYYY:MM:DD:hh:mm:ss Z info vpxd[31761] [Originator@6876 sub=MoCluster opID=53d75ece-01-01-01-5e2f242e] Host [vim.HostSystem:<PNID OF ESXI HOST>] has 1 HDCS resources
YYYY:MM:DD:hh:mm:ss Z info vpxd[31761] [Originator@6876 sub=Invt opID=53d75ece-01-01-01-5e2f242e] Started call to update entity state moId on host; [vim.HostSystem:<PNID OF ESXI HOST>>], store: (vm, XXXX), v: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXX:vm-XXXX:2f2PavDPxnApna395mPFE0y0yUuuSwxhuGWCDdJV59E=, callId: 3
YYYY:MM:DD:hh:mm:ss Z info vpxd[31655] [Originator@6876 sub=DAS opID=53d75ece-01-01-01-5e2f242e-AsyncReportHdcsVm-665114b5] [VpxdDasConfig::PushConfigToFDM] pushed config version 1073857  to host [vim.HostSystem:<PNID OF ESXI HOST>>] (cluster [vim.ClusterComputeResource:domain-c225,<Cluster_name>])
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=VmProv opID=53d75ece-01-01-01] Created VM vim.VirtualMachine:vm-544303 (ds:///vmfs/volumes/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXX/vCLS-403a6341-fedc-4895-XXXXXXXXX/vCLS-XXXXXXX-XXXX-XXXX-XXXX-XXXXXXX.vmx) on host [vim.HostSystem:<PNID OF ESXI HOST>] (<<PNID OF ESXI HOST>)
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=VmProv opID=53d75ece-01-01-01] Action timings:
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=vpxLro opID=53d75ece-01-01-01] [VpxLRO] -- FINISH lro-756
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=vpxLro opID=53d75ece-01-01] [VpxLRO] -- FINISH lro-755
YYYY:MM:DD:hh:mm:ss Z warning vpxd[31648] [Originator@6876 sub=vpxUtil opID=53d75ece-01] getaddrinfo failed; host: <PNID OF ESXI HOST>, e: N7Vmacore15SystemExceptionE(Name or service not known)
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=MoHttpNfcLease opID=53d75ece-01] Host URL:https://<PNID OF ESXI HOST>/nfc/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXX/, target ID: disk-0.vmdk
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=VAppImport opID=53d75ece-01] Import task progress: 1
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=VAppImport opID=53d75ece-01] Import task progress: 2
YYYY:MM:DD:hh:mm:ss Z error vpxd[31648] [Originator@6876 sub=VAppImport opID=53d75ece-01] Caught exception while importing VM: N5Vmomi5Fault15RequestCanceled9ExceptionE(Fault cause: vmodl.fault.RequestCanceled
YYYY:MM:DD:hh:mm:ss Z info vpxd[31648] [Originator@6876 sub=VAppImport opID=53d75ece-01] Removing VM [vim.VirtualMachine:vm-XXXX,vCLS-XXXXXXX-XXXX-XXXX-XXXX-XXXXXXX] due to failed import
YYYY:MM:DD:hh:mm:ss Zinfo vpxd[31648] [Originator@6876 sub=VAppImport opID=53d75ece-01] Done cleaning up after failed import


        

Environment

 

 

Cause

The issue is due to the wrong DNS entry of ESXI host and vCenter server or if there are any issues with name resolution.

Resolution

Ensure the correct DNS server is configured in vCenter server and ESXI Host.

If the issue still persists, make sure the nslookup works for both forward and reverse lookup for the PNID of host and vCenter server.

Powered by Wolken Software