Hard to tell from the error without seeing the system (might need to experiment or call support)
Here are a few things I would check (taking guesses from looking at the log)
The ESX host that the VM is currently on, does it have the VCD agent showing as valid in the vCloud Admin interface? (all hosts in cluster enabled with valid agent showing in vCloud?)
The VDC this vApp is on, is it paygo or does it have resource limitations (like reservation)
It appears it is having trouble starting a VM bases on one of these things:
cpu- needs to reserve 88mhz (seems like this is small and might not be issue)
mem - need to reserve - 16384 MB (16GB) does the resource pool this VM is in have this many free resources, - one test is create a new vm in vCenter, place in SAME pool and set mem to 16GB reservation and 32 GB total - will it start?
cpu-count - 4 vcpu; unless this is very dense cluster I assume this is ok - maybe toss that setting in the test vm as well
datastore space - moref=60072 for the datastore - check whatever datastore that is, make sure you have space free
I know this might not be the issue; but from the log that is the first place I would start (make a test VM using vCenter and see how close you can match it up to make sure it works - same resource pool is important; disk size I expect is not the issue so test vm could have very small disk for test)