vRealize Orchestrator Appliance 8.1.0 Patch 2 | 29 July 2020 | Build 16631446
Check frequently for additions and updates to these release notes.
VMware vRealize Orchestrator 8.1.0 Patch 2 is a minor product patch release that includes specific resolved issues and common improvements made across the vRealize Orchestrator platform. The content of the VMware vRealize Orchestrator 8.1 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 2
You can upgrade your vRealize Orchestrator Appliance to the Patch 2 build by following the official upgrade procedure. See Upgrade a Standalone vRealize Orchestrator 8.0.1 Deployment.
- For user interactions, the external values drop-down menu used to filter actions by return type fails to display the object.
The workflow variable types mapped as input parameters for user interactions are not transferred correctly to the workflow input form.
- An incorrect email is displayed during a push operation.
When performing a push operation to a remote Git repository, the displayed author email is the default email configured in vRealize Orchestrator and not the actual user email.
- When migrating vRealize Orchestrator 7.4 or earlier, the migration script fails on "Validates Orchestrator database content." step, while displaying the help output of the db-validate script.
When the database password contains special characters, this causes the db-validate script to fail.
- You cannot duplicate a workflow in the same folder as the source workflow.
You cannot duplicate a workflow in the same folder as the source workflow. The duplicate is moved to the web-root folder.
- You cannot configure local sites in the SRM plug-in.
When you use a vRealize Orchestrator deployment authenticated with vRealize Automation, you cannot configure local sites in the SRM plug-in. The workflow fails with the following error: "ReferenceError: "SRMPluginConfig" is not defined."
- The workflow run fails if you have an attribute that uses a Composite type with a Object reference field value passed as a input parameter to an embedded workflow.
The workflow run fails with a validation error when the workflow triggers an embedded workflow that includes composite type objects that contain the plug-in type.
- The "Add Key" workflow finishes successfully, but no key is found in the Certificate Authority keystore.
When you add custom keys, such as a RSA private key, by using the "Add Key" workflow, the workflow run finishes successfully, but the key is not added to the keystore.
- Issues when viewing content on the Scripting tab
When opening the Scripting tab, such as the tab in the Scriptable task workflow element, the script field expands continiously, which can cause memory load issues.
- Orchestrator Administrators in vRealize Automation are unable to create Python, Node.js, or PowerShell actions and scripts.
After upgrading to vRealize Orchestrator 8.1.0 Patch 2, administrator users are unable to create Python, Node.js, or Powershell actions or scripts. To use these scripting languages, the users need Orchestrator Workflow Designer rights.
1. From the vRealize Automation settings menu, select Identity & Access Management.
2. Select your administrator user.
3. Click Edit Roles.
4. Click Add Service Access.
5. From the left drop-down menu, select Orchestrator.
6. From the right drop-down menu, select Orchestrator Workflow Designer.
7. Save your changes.
8. If the user with edited rights is currently logged in, they must log out and log back in for the changes to take effect.
- 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.
- 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