[VMC on AWS] OVA deployed via content library gets incorrect disk size

Products

• VMware Cloud on AWS

Issue/Introduction

Created to explain the issue as it is known now and provide a way for the customer to track this issue.

Symptoms:
The deployment of a VM from OVA leaves a VM created with two disks. 20gig and 2 gig. Once deployed the 2 gig disk is correct but the 20 gig disk is created as 1gig and is manually resized to 20 gig.

This shows that 2 disks were sized to be 2 GB and 20 GB

This show the completed deployment with two disks.  One is the 2GB disk and the second is the erroneously sized disk of 1 GB.  This 1GB disk was expected to be 20GB.
This occurs when the OVA is deployed from the content library.

Cause

The issue is somewhere in the resize of the disks. When deploying through Content Library, you get the disk sizes that are defined in the .vmdk files.
For instance for the data-disk, the predefined size is exactly 1GB:

The OVF spec shows:
vmware-Tst-1.20-x86_64-1.2.0-1d9774bf.ovf
    <File ovf:id="file1" ovf:href="vmware-tst-1.20-x86_64-1.2.0-1d9774bf.vmdk"/>
    <File ovf:id="file2" ovf:href="vmware-tst-k8s-1.20-x86_64-1.2.0-1d9774bf-data.vmdk"/>
  </References>
  <DiskSection>
    <Info>List of the virtual disks</Info>
    <Disk ovf:capacityAllocationUnits="byte" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:diskId="vmdisk1" ovf:capacity="2147483648" ovf:fileRef="file1"/>
    <Disk ovf:capacityAllocationUnits="byte" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" ovf:diskId="vmdisk2" ovf:capacity="21474836480" ovf:fileRef="file2"/>
Calculation of Disk 2
21474836480/1024=20971520
 20971520 /1024=20480
20480 / 1024=20 GB
 
The OVA specs shows:
Calculation of Disk 2
vmware-Tst-1.20-x86_64-1.2.0-1d9774bf-data.vmdk
RW 2097152 SPARSE "vmware-Tst-1.20-x86_64-1.2.0-1d9774bf-data.vmdk"
2097152 * 512 / 1024 / 1024 / 1024 = 1 GB
2097152 * 512=1,073,741,824
1,073,741,824 / 1024 = 1048576 
1048576 / 1024=1024
1024 / 1024=1GB

Resolution

There is no resolution for this issue at this time.

Workaround:
After creation of the VM is completed, adjust the effected disk to the proper or expected size manually.
Another option is to deploy via direct upload of the OVA.