"Invalid vApp properties: Argument 'NETWORK_NAME' not a valid network name" error when attempting to deploy a vApp from a vApp Template in Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Attempting to deploy a vApp from a vApp Template in Cloud Director.
• The vApp Template was imported to a Catalog from an OVF/OVA.
• The vApp deployment fails with an error in the Cloud Director cell /opt/vmware/vcloud-director/logs/vcloud-container-debug.log similar to:

| ERROR    | task-service-activity-pool-123 | FutureUtil                     | Failed to deploy VM | requestId=<REQUEST_UUID>,request=POST https://<VCD_URL>/api/vApp/vm-<VM_UUID>/power/action/powerOn,requestTime=<REQUEST_TIME>,remoteAddress=<CLIENT_ADDRESS>,userAgent=<CLIENT_ADDRESS>,accept=application/*+xml;version 36.3 vcd=<VCD_UUID>,task=<TASK_UUID> activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:<TASK_UUID>)
com.vmware.ssdc.util.LMException: Invalid vApp properties: Argument '<NETWORK_NAME>' not a valid network name.,Argument '<NETWORK_NAME>' not a valid network name.,Argument '<NETWORK_NAME>' not a valid network name.,Argument '<NETWORK_NAME>' not a valid network name..
        at com.vmware.ssdc.backend.DeployVAppVmSubsetActivity$CustomizeVmsPhase.customizeVms(DeployVAppVmSubsetActivity.java:286)
        at com.vmware.ssdc.backend.DeployVAppVmSubsetActivity$CustomizeVmsPhase.invoke(DeployVAppVmSubsetActivity.java:249)

Environment

VMware Cloud Director 10.x

Cause

This is a known issue affecting Cloud Director 10.3.3 when deploying vApps from vApp Templates created by importing OVF/OVAs into a Catalog.

Resolution

This issue is resolved in Cloud Director 10.3.3.4 which is available here, VMware By Broadcom Downloads.