vRealize Orchestrator Appliance 8.2 Patch 1 | 12 November 2020 | Build 17157891
Check frequently for additions and updates to these release notes.
VMware vRealize Orchestrator 8.2 Patch 1 is a minor product patch release. The content of the VMware vRealize Orchestrator 8.2 Release Notes apply to this version as well.
What's in the Release NotesThe release notes cover the following topics:
ImportantUpgrade failure after performing steps in KB 87120
Performing the instructions used to address the CVE-2021-44228 and CVE-2021-45046 log4j vulnerabilities described in KB 87120 can cause upgrade failures for vRealize Automation and vRealize Orchestrator 8.6.2 or earlier. For a workaround, see KB 87794.
How to upgrade to Patch 1
You can upgrade your vRealize Orchestrator Appliance to the Patch 1 build by following the official upgrade procedure. See Upgrade a Standalone vRealize Orchestrator 8.0.1 Deployment.
- When importing packages that are larger in size than allowed, you see a message stating that the upload failed with a status code 500.
By default, the maximum size for imported packages is 50 MB. If you try to import packages that are larger than 50 MB, you see a message that the upload failed.
- Some content imported from vRealize Orchestrator 7.6 cannot be deleted in vRealize Orchestrator 8.x.
Library workflows imported from vRealize Orchestrator 7.6 to vRealize Orchestrator 8.x cannot be deleted as a dependency of a custom content as those Library workflows are read-only. You might want to delete them as they existed in vRealize Orchestrator 7.6 and do not exist in vRealize Orchestrator 8.x but are imported with the package. Git errors can occur in relation to some of these workflows using characters that were valid in vRealize Orchestrator 7.6 but not vRealize Orchestrator 8.
- After upgrade, the Waiting for input category shows zero workflow tokens.
After upgrade, the number of tokens in a Waiting state that appear in the Workflow Runs and Waiting for input categories is different.
- Using the vRealize Orchestrator scripting to create and update configurations or resources can lead to incorrect or missing version history.
When you update configurations and resources through the vRealize Orchestrator scripting API without explicitly calling the
saveToVersionRepositorymethod, version history is not generated for that content. This can cause issues if an external Git integration is added post upgrade.
Workaround: Before upgrading to vRealize Orchestrator 8.2 Patch 1, make sure that you save any changes you made trough the scripting API. See KB 81575.
- Custom content is not available in Git history after migrating vRealize Orchestrator 7.5 to vRealize Orchestrator 8.x.
After migrating vRealize Orchestrator 7.5 to vRealize Orchestrator 8.x, when you configure your Git integration, custom content is not available in Git history.
Workaround: To see all migrated content as local changes in Git, manually edit and save custom content to convert it to an 8.x-compatible format before you make an initial push to the repository. After that, you can push all migrated content to your Git repository.
- Scheduled workflow runs are triggered at a different than the expected time with the time offset to UTC time.
When you schedule workflow runs through scripting by using the
*workflow.scheduleRecurrently()*function, scheduled workflows are always triggered in UTC time. There is a discrepancy between the vRealize Orchestrator Client UI and the function behavior, because the UI adds the time zone of your browser to the recurrence pattern. However, the time zone is not included in the recurrence pattern when using the function and the calculations of the time to the trigger the workflow runs are done on the server side in UTC time.
Workaround: When you schedule workflow runs in scripting, use time values in UTC time.
- Unable to properly save variables of the Regexp type in the Variables editor. Incorrect values are displayed in the editor.
This issue is caused by the
Regexptype variables being misinterpreted as special objects instead of strings.
Workaround: Switch to using
stringtype variables as they are an equivalent of
- Duplicated workflows created in Orchestrator Legacy Client might display a constant instead of an external action in their value options.
When editing the input parameters of a workflow that is designed in the Orchestrator Legacy Client, and duplicated in the vRealize Orchestrator Client, the value options might be set as a constant instead of an external action.
Workaround: Navigate to the Input Form tab and edit the input parameter presentation to include the required external action.
- Unable to select an action as an external source in input forms because of a return type issue.
In the vRealize Orchestrator Client Input Form tab, you are unable to select an action that has a return type of either
Array/Anyfor a default value or value option.
1. Log in to the vRealize Orchestrator Client.
2. Select your workflow and navigate to the Input Form tab.
3. Set the action with the return type expected from the widget default value or value option and save the changes.
4. Select the default value or value option action, save the workflow, and revert the action to previous version or change the return type back to the