Configuration and Resource Elements are reverted to an older version after upgrade to vRealize Orchestrator 8.2

Products

• VMware

Issue/Introduction

This issue is specific to how vRealize Orchestrator resource elements and configuration elements are used in your environment. These may contain values related to your hosts, networks, or other key data that is used as part of the workflow execution. This will only occur when upgrading from any vRealize Automation or vRealize Orchestrator 8.x to version 8.2 builds and will result in these objects losing the stored data.

Symptoms:
Workflows with configuration elements and resource elements may have unintended results post upgrade, the workflows are reverted to the last time a manual update was made without the scripting API or to the original version of the configuration.

Cause

Resource and configuration elements could be reverted to a previous version if the saveToVersionRepository method was not invoked after performing the element update to synchronize the data with the version repository.

Resolution

The upgrade issues have been addressed, please download the latest upgrade ova bundle, vrlcm-vra-8.2.0-8.2.0.12959.ovabundle, for 8.2 and proceed with the upgrade.

Note:  Before upgrading to vRealize Automation 8.2, you must apply Product Support Pack 1 on vRealize Suite Lifecycle Manager 8.2.

Additional Information

How to Download vRealize Suite product patches in Customer Connect

Impact/Risks:

• If the scripting API was not used to execute the update to these elements, then you will not be affected.
• If you are using this publicly available content, you may be impacted by this issue:
  • Posted at code.vmware.com: vRealize Automation 7x: Guest script manager package. Instructions have been added to prevent this issue until the fix is available and an updated package will also be provided.
  • Posted at VMware blogs: Using Custom Resources to Execute Scripts along with Deployment

Note: This issue impacts embedded vRealize Orchestrator instances on vRealize Automation appliances and standalone instances of vRealize Orchestrator.  Fresh installations (non-upgrade) are not affected.