The operation failed because no suitable resource was found.

[thomps01]

Using vCloud Director 5.1 when I attempt to import a virtual machine from vSphere, it fails with the following message:

"The operation failed because no suitable resource was found."

I can deploy new virtual machines into the same organisation from the public catalog and they work fine.

The VM which is failing to import can be imported without issue to other organisations but for some reason I can't import it to this one org.

Any ideas?

I'm using a Pay as You go allocation model and have plenty of resources available.

Update:

I can import the virtual machine from vSphere into the public catalog, make it a gold master and then deploy it without issue to any org.

[IamTHEvilONE]

No suitable resource is about trying to allocate some resource to the VM.  CPU/Memory is from OvDC, Storage is from a Storage Profile in the OvDC, network, etc.  There is also the process of allocating a resource to do the copy/move as required from vCenter to vCloud Director.

Using vCloud Director 5.1 when I attempt to import a virtual machine from vSphere, it fails with the following message:

"The operation failed because no suitable resource was found."

Update:

I can import the virtual machine from vSphere into the public catalog, make it a gold master and then deploy it without issue to any org.

So is the issue not happening anymore?  The update is somewhat contradictory to the original issue.  Are you attempting to import the VM directly into a vApp and get the error message?  If the vApp is powered on, we will try and place the new VM into the same network/OvDC pool as the vApp itself.  This may cause problems if we cannot expand the pool for reservation purposes.

[thomps01]

It's a really odd issue.

The OVDC has plenty of resource available (hence the ability to deploy vApps from a catalog without issue).

The storage profile has around 15TB free space.

The VM being imported is powered off.

The vApp the VM is being imported into is also powered off.

Because I've now managed to work around the issue by creating a gold image to deploy from inside the public catalog it's not stopping me working but I will attempt to resolve this issue in-case it happens again.

[IamTHEvilONE]

can you file a support ticket for this, or post the vcloud-container-debug log file that has the error state involved?  Just know posing the debug file may contain some sensitive information (ip of the vCloud Cell as an example).