Hello,
We recently came across what we suspect to be a bug in vCloud Director 9.1 and 9.5, and possibly higher, although we have not tested any other versions.
Affected versions:
9.1 (don't have build number sorry)
9.5 build 12982517
The issue:
Importing an OVF file that does not contain the <OperatingSystemSection> information into vCloud Director via the Tenant portal GUI results in the following:
Importing the exact same OVF into vCloud Director via the Flex /cloud interface or directly into the vCenter (6.5.0.20000) works fine.
The resolution:
After successfully importing other vApps via the Tenant portal and comparing them with the vApp that failed, we discovered that the failing vApp was missing the <OperatingSystemSection> details in the OVF. After adding in the below section to the OVF, importing the OVF via the Tenant portal worked fine.
<OperatingSystemSection ovf:id="85" ovf:version="12" vmw:osType="sles12_64Guest">
<Info>The installed guest operating system</Info>
<Description>SUSE Linux Enterprise 12 (64-bit)</Description>
</OperatingSystemSection>
Conclusion:
We believe this is a bug in vCloud Director because the Tenant portal should perform either of the below options, as opposed to crashing the GUI:
Cheers,
Thomas
It's good to see that VMware take bug reports so seriously.
It's good to see that VMware take bug reports so seriously.