The vApp deployment fails during the subnet node binding process

Products

• VMware Cloud Director

Issue/Introduction

vApp deployment fails with the following traces in the networking.log

2025-xx-xx 15:xx:xx,484 | DEBUG    | Backend-activity-pool-453455 | IpSubnetNodeServiceImpl        | Failed to bind subnet node with static pool address mode | requestId=####-####-####-####-########,request=POST https://vcloud.example.com/api/vdc/#######-####-####-####-############/action/composeVApp,requestTime=1745420748172,remoteAddress=10.xx.xx.xx:20498,userAgent=Java/1.8.0_401,accept=application/*;version 35.0 vcd=#######-####-####-####-############,task=#######-####-####-####-############ activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-############) activity(com.vmware.vcloud.vdc.impl.ComposeRecomposeVAppActivity,urn:uuid:########-####-####-####-############)
2025-xx-xx 15:xx:xx,484 | DEBUG    | Backend-activity-pool-453455 | IpSubnetNodeServiceImpl        | Failed to get an IP from BindNextFreeIpRunnable after 15 number of attempts | requestId=####-####-####-####-########,request=POST https://vcloud.example.com/api/vdc/#######-####-####-####-############/action/composeVApp,requestTime=174########,remoteAddress=10.xx.xx.xx:20498,userAgent=Java/1.8.0_
401,accept=application/*;version 35.0 vcd=#######-####-####-####-############,task=#######-####-####-####-############ activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-############) activity=(com.vmware.vcloud.vdc.impl.ComposeRecomposeVAppActivity,urn:uuid:########-####-####-####-############)

 

Environment

10.x

Cause

The suspected cause is the inability to allocate an IP address for the vApp, potentially due to a lack of available IPs in the relevant pool or an incorrect IP address allocation mode configured in the deployment request. 

Resolution

If using a POOL IP allocation mode, ensure IP addresses are available in the pool