In vCD 1.5 I could import a vSphere VM into vCD without causing a clone. The conditions for this were basically:
1) The VM and all of its files and volumes were on a single datastore.
2) The datastore was part of the Provider vDC containing the Org vDC into which I was importing.
3) The datastore was enabled.
When importing a vSphere VM into vCD 5.1, when the VM is on a datastore that is part of a datastore cluster, it seems that I cannot reliably avoid the clone. Basically, it appears that vCD always chooses a new datastore on which to place the VM. On some occasions it will choose the datastore that the VM is already on, which means that the clone will be avoided. However, in other cases, it will clone. This can happen even if the datastore is part of a storage profile that's assigned to both the Provider vDC and the Org vDC, in which case I would not have expected it to clone hte VM.
This is causing me a great deal of trouble for two reasons:
1) The clone operation can be very long; and
2) The clone operation creates a new moref for the vSphere VM, but does not return it, which means I have to find it by myself.
Is there a reliable way to convince vCD to leave the VM on the same datastore?