vApp option properties change order when cloning as template to content library

Products

• VMware vCenter Server

Issue/Introduction

When choosing clone as template and moving to content library, vApp option properties added get scrambled and do not show the same order as in template customization spec.

Environment

vCenter 8.x

vCenter 7.x

Cause

This is expected behaviour as per the current CLS backend logic. While exporting the VM as an OVF template using CL, the property's order is not maintained in the OVF template.

Resolution

This is currently being worked on by VMware Engineering to preserve the order of properties, so that the order in which the user configures will be retained after exporting the OVF using content library. It will be fixed in a future release of vCenter.