this might be the same issue .... if you have 750GB ... we may check to see if you have ((750 + 40) * 2) to be free. It's like we check to make a full clone on the same datastore.
This logic is not correct, and we are working on it
You also cannot make a disk that would put you past the red threshold of the Datastore itself. the default is 15% of the Datastore. so if you have a 2 TB lun, there is 300GB reserved ... we are requesting close to 1600GB of space. ... so if you have any other VM on this datastore, it may fail. If you cross yellow ... it may also fail ... yellow is 25% by defualt (so 1.5TB).
The placement logic is improved in 5.1.2, and will continue to be improved.
The log is vcloud-container-debug.log ... grep through all of them for the "There is no hub to satisfy the requirement" message. Alternatively, grep for "The operation failed because no suitable resource was found."
I'm just putting both messages since they are typically intermingled. attach the entire log file which contains the error state, and I can evaluate it.
The latter error was addressed in some situations in 5.1.2 under the following release note:
"Attempting to power on a virtual machine fails with a no suitable resources error
Fixed a problem that could cause adding a new virtual machine to a vApp to fail with the following error: The operation failed because no suitable resource was found."
This is the main reason I am asking if you can upgrade.
