VM Import from vCenter to Existing vApp Fails with "No suitable resource was found" in VMware vCloud Director

Products

• VMware Cloud Director

Issue/Introduction

When attempting to import a Virtual Machine (VM) from vCenter into an existing vApp via the VMware Cloud Director UI, the operation fails. The failure occurs because the system incorrectly rejects the available VM groups and datastores.

• The import process is initiated via the UI path: Data center > vApps > All Actions > Import VM from vCenter.

• The vcloud-container-info.log file, located at /opt/vmware/vcloud-director/logs/, will show errors confirming that storage containers were rejected due to storage policy mismatches:

  java.util.concurrent.ExecutionException: com.vmware.vcloud.api.presentation.service.InternalServerErrorException: The operation failed because no suitable resource was found. Out of 8 candidate hubs:
1 storage containers rejected because: They are not accessible to any ESXi hosts.  Rejected storage containers: <container_name>
36 storage containers rejected because: They do not support the required storage policy: <Storage_policy_name>.  Rejected storage containers: <Storage_policy_name>
<Storage_policy_name>, <Storage_policy_name>, <Storage_policy_name>

Environment

VMware vCloud Director 10.6.x

Cause

This is a known issue in VMware Cloud Director, where the imported disk details are omitted from the backend request payload.

Because the backend does not receive the storage policy details selected by the user for the imported disk, it automatically defaults to the standard storage policy of the Organization Virtual Data Center (Org VDC) where the VM is being imported. This mismatch causes the system to evaluate and ultimately reject the available storage containers, assuming they do not support the required (but incorrectly applied) storage policy.

Resolution

This issue will be addressed in a future release of VMware Cloud Director.