wrote:
Then, instead of selecting the OVA in the deployment wizard, select the extracted files except for the .mf file.
Thanks, that (skipping the .mf file during import) did it for me with two OVF templates I was trying to import. (7.0u3)
I checked and re-checked the files and their hashes (and hash types - all SHA1), and my current working theory is that long file names containing parentheses (e.g. "OU01-VMtype007-ID673 (template clone 2024-02-15).nvram") confuse vCenter to a point of erroring out.
P.S. The error:
Failed to deploy OVF package. ThrowableProxy.cause A specified parameter was not correct: The provided manifest file is invalid: Invalid OVF checksum algorithm: SHA1(OU01-VMtype007-ID673 .
I.e. the filename in the error was truncated right before the first parenthesis.