"Max attempts to deploy on compute fabric exceeded configured value" when powering on VMs in VMware Cloud Director
Article ID: 436003
Updated On:
Products
Issue/Introduction
When attempting to instantiate VMs, or migrate VMs using VMware Cloud Director Availability to VMware Cloud Director, an error in /opt/vmware/vcloud-director/logs/vcloud-container-debug.log is received similar to:2026-03-29 04:11:29,356 | ERROR | Backend-activity-pool-6806 | FutureUtil | Failed to deploy VM fabrics, VM id: fabricFuture | requestId=UI-#########################,request=POST https://<Cloud Director FQDN>/api/vApp/vapp-###################/power/action/powerOn,requestTime=1774757483932,remoteAddress=###########:16648,userAgent=Apache-HttpClient/4.5.14 (Java/17.0.12),accept=application/*+xml;version 38.0 vcd=#################,task=############## activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:##################) activity=(com.vmware.ssdc.backend.services.impl.DeployVAppActivity,urn:uuid:####################) activity=(com.vmware.ssdc.backend.DeployVAppVmSubsetActivity,urn:uuid:#######################)java.lang.Exception: Max attempts to deploy on compute fabric exceeded configured value at com.vmware.ssdc.backend.DeployVmOnFabricsActivity$DeployVMsComputeFabricPhase.invoke(DeployVmOnFabricsActivity.java:190) at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase(ActivityRunner.java:175) at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:112) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)
Virtual machine operation tasks fail on VMware Cloud Director - 'Max attempts to deploy on compute fabric exceeded configured value' has already been checked, and there are sufficient resources available.
Environment
VMware Cloud Director 10.6.x
Cause
There are too many concurrent updates to the same resource pool in Cloud Director causing an error in how the available resources are retrieved. Earlier in the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log there is an error updating the resource pool available resources:2026-03-29 04:10:41,508 | INFO | Backend-activity-pool-6624 | Conversation | Transaction rolled back; session has been closed [Conversation: ##################, transaction null, transactionDepth: 0] Transaction opened at: <undefined>current stack: java.lang.Exception at com.vmware.vcloud.common.persist.Conversation$1.getNewText(Conversation.java:98) at com.vmware.vcloud.logging.DecoratedLogger.info(DecoratedLogger.java:153) at com.vmware.vcloud.common.persist.Conversation.rollBackTransactionIfActive(Conversation.java:373) at com.vmware.vcloud.fabric.compute.dao.impl.HibernateAbstractHandleableDao.rollBackTransactionIfActive(HibernateAbstractHandleableDao.java:195) at com.vmware.vcloud.fabric.compute.dao.impl.HibernateAbstractHandleableDao.incrementVersion(HibernateAbstractHandleableDao.java:222) at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.applyResourceReconfig(GenericVirtualResourcePool.java:1391) at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.reconfigureOtherResourcePoolsForNonFlexVdc(GenericVirtualResourcePool.java:1434) at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool$ReconfigOtherResourcePoolRunnableContext.run(GenericVirtualResourcePool.java:5160) at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool$ReconfigOtherResourcePoolRunnableContext.run(GenericVirtualResourcePool.java:5141) at com.vmware.vcloud.common.persist.ConversationContextExecutor.execute(ConversationContextExecutor.java:67) at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool$3.run(GenericVirtualResourcePool.java:4568)
This resources in an invalid state in the resource pool:2026-03-29 04:10:43,531 | DEBUG | Backend-activity-pool-6630 | GenericVirtualResourcePool | vrp <Resource Pool Name> (####################):################### - Invalid state on sub resource pool with id ########################. Going to retry. | requestId=UI-#######################,request=POST https://<Cloud Director FQDN>/api/vApp/vm-###################/action/reconfigureVm,requestTime=1774757438829,remoteAddress=############:43597,userAgent=Apache-HttpClient/4.5.14 (Java/17.0.12),accept=application/*+xml;version 38.0 vcd=#####################,task=#################### activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:###################) activity=(com.vmware.ssdc.backend.services.impl.RelocateVmActivity,urn:uuid:#########################)
Resolution
There will be a code change in the next major patch release of VMware Cloud Director (after 10.6.1.2). There are two potential options in the meantime:
- A retry setting can be configured With the cell-management-tool. This can impact performance and the load on Cloud Director as it's increasing retry amounts. The value can be set to 20, 40, 60, but it is not recommended to go higher than 40. It does not require a restart of services. The command is: /opt/vmware/vcloud-director/bin/cell-management-tool manage-config -n EvdcResourcePoolConfig.retryCount -v 40
- Reduce the workload on VMware Cloud Director that caused the error. This could be the result of automation or multiple migrations from VMware Cloud Director Availability. The workload should be reduced so that Cloud Director can update the resource pool in a timely manner without locking the entry in the database.
Feedback
