vApp or vApp Template containing a VM with 4 IDE disks won't copy or deploy from catalog as template in Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• Unable to deploy a VM with four IDE disks using the catalog template page workflow. The deployment fails with the error: 

  “Can’t find free address for bus with Type=5 and sub Type=Null.”

• Error in vcloud-container-debug.log: 

  ERROR    | Backend-activity-pool-######| CopyContentsActivity           | [Activity Execution] Uncaught Exception during Activity execution. Recent phase: com.vmware.vcloud.vdc.impl.CopyContentsActivity$CopyContentsPhase@###### - Handle: urn:uuid:#####-####-####-####-#########, Current Phase: CopyContentsActivity$CopyContentsPhase | requestId=#####-####-####-####-#########,request=POST https://api/catalog/######-####-####-####-#########/action/captureVApp,requestTime=##########,remoteAddress=###.##.#.#:#####,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+xml;version 39.0 vcd=#####-####-####-####-#########,task=#####-####-####-####-######### activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:#####-####-####-####-#########) activity=(com.vmware.vcloud.vdc.impl.CopyContentsActivity,urn:uuid:#####-####-####-####-#########)
  java.util.concurrent.ExecutionException: com.vmware.ssdc.util.LMException: No available IDE slot for the new IDE hard disk
          at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:136)
          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)

Environment

• VMware Cloud Director 10.6.x

Cause

This is a product limitation in VMware Cloud Director (VCD) deployment with 4 IDE disks.

Resolution

The issue will be fixed in a future release of 10.6.x.

For further clarification, contact Broadcom Support and note this Article ID (444943) in the problem description. For more information, see Creating and managing Broadcom support cases.