VSphere vApp Notes and Start Order Not Retained After vCenter Reboot or VPXD Service Restart

Products

• VMware vCenter Server

Issue/Introduction

After creating a vApp from the VCenter UI, adding or making changes to the notes, the VM start order or other properties are not retained after the VCenter server is rebooted or VPXD service is restarted. 

Environment

VCenter 8

VCenter 9

Cause

Changes to vApp properties are not written to the VCenter database due to a known issue with a "no-commit" defect and remain in VPXD memory until the service is restarted or VCenter is rebooted.

Resolution

1. Create a default resource pool that neighbors the vApp in the cluster inventory. It is recommend to leave it with the default settings, with zero shares but fully expandable. This should avoid disrupting any running VMs contained in vApps when the vApp is moved into, or out of it.

2. Move the vApp into the default resource pool. This updates its configured parent which is an operation that isn't affected by the defect. The vApp configuration is then written to the database.

NOTE: Moving the vApp in or out of the resource group triggers the write. Changes made while the vApp is stationary (inside or outside of the resource group) will NOT be saved after vCenter reboot or VPXD service restart.

Additional Information

This defect will be fixed in an upcoming patch release for vCenter 8 and 9.