Invalid checksum algorithm in OVA manifest for PMM-1.2.0

We fixed this in PMM 2.2 in

I am fully aware that this can be done... along with using something like clonezilla or other tools to convert the extracted vmdk to another format.  Those are just hacks.  If Percona is going to provide an OVA to be used in more enterprise environments then the OVA needs to function within a vSphere environment.  If there is no want to get the OVA to function then they need to remove it and inform customers that this is not a viable option.  After reviewing the forum post, this looks like more a problem beyond VMware and if Percona needs access to these enterprise virtualization solutions then maybe contacting a customer might help.

Hi, try to deploy it directly at the vmware host using ESXi embedded host (after decompressing OVA (is a .GZ) and deleting internal .MF file)

See https://www.percona.com/forums/questions-discussions/percona-monitoring-and-management/51005-is-there-a-yum-repo-available-for-pmm

This is still an issue even with the latest version, 1.8.0.  I am unable to import the ovf into vCenter 5.5 and 6.5.  If gives the invalid OVF checksum algorithm: SHA1 error.  

Hi , - unfortunately we do not have access to vCenter in order to test these images correctly.  Would either of you happen to have a Percona Support agreement?  This will impact whether we can address your request.  Thanks,