In the previous version of CloudForms, cloning a VMware template failed when the target datacenter was nested below multiple folders. This was because if the datacenter was nested logically under various folders, users were unable to find the placement ID during an autoplacement VMware provision request.
This fix always does a lookup of the folder path from the host datacenter instead of statically setting a possible wrong default value which has resolved the issue.
Cloning this template works fine but "provision from VM" fails with error "
[RuntimeError]: A specified parameter was not correct. spec.location.folder "
Not alive anymore .
All appliance stay for a day or two max (until they hit the SWAP memory issue, once they hit SWAP we have to kill them )
I will try and recreate on another appliance .
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2839.html