vRealize Orchestrator Appliance 8.1 | 14 April 2020 | Build 15995344
Check frequently for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New in vRealize Orchestrator 8.1
- Deploying the VMware vRealize Orchestrator 8.1 Appliance
- Upgrading and Migrating to vRealize Orchestrator 8.1
- Root Password Expiry Extension
- Plug-ins Installed with vRealize Orchestrator 8.1
- Internationalization Support
- How to Provide Feedback
- Prior Releases of vRealize Orchestrator
- Resolved Issues
- Known Issues
What's New in vRealize Orchestrator 8.1
Enhanced Ease of Use, and DevOps Automation
vRealize Orchestrator 8.1 delivers powerful feature enhancements, that improve the productivity, efficiency, and effectiveness of IT/Cloud admins and DevOps admins, who are modernizing their data center infrastructure using vCloud Suite, and VMware Cloud Foundation. Key features include:
Tree view of hierarchical folders. vRealize Orchestrator 8.1 reintroduces support for tree views of hierarchical folders, so users can organize, view, and browse their vRealize Orchestrator objects in a hierarchical tree view. The Tree View allows for easier management of objects at scale, giving users a global view of all organized content. See Create a Folder or Subfolder in the vRealize Orchestrator Client.
Run and debug actions. Users can run and debug an action without having to add the action to a workflow and then having to perform a workflow run. Each action can be unit tested prior to running the associated workflow, enabling accelerated workflow development. See Running and Debugging Actions.
- Debug workflow schema. Users can debug a workflow by setting breakpoints on specific elements in the workflow schema. See Debug Workflows by Schema Element.
Push change sets to Git branches. When versioning content in a Git repository, vRealize Orchestrator allows users to select, configure, and push change sets to different branches from a Git repository. This enables users to promote vRealize Orchestrator content through standard Git operations. See How Can I Use Git Branching to Manage My vRealize Orchestrator Object Inventory.
- Syslog support. You can configure a logging integration to one or more remote syslog servers. See Create or Overwrite a Syslog Integration in vRealize Orchestrator.
- vSphere 6.7 plug-in API update. The vSphere plug-in API has been updated to support version 6.7.
[Important] Feature and Support Notices
- Python, Node.js, and PowerShell script languages are available only for vRealize Orchestrator instances that use a vRealize Automation license.
- The duplicate option for vRealize Orchestrator objects, such as workflows, actions, policies, configurations, and resources is not available in Tree View. You can duplicate objects from the Card View.
- Preinstalled vRealize Оrchestrator actions cannot be duplicated. To duplicate such actions, create a new action and manually copy the relevant script, input parameters, and return type.
- vRealize Orchestrator internal content synchronization might delay the service startup with few minutes. This can lead to the vRealize Orchestrator service being unavailable during failover events or during cluster node failures.
- vRealize Orchestrator 8.x introduces a new procedure for adding a JDBC connector for the SQL plug-in. See Adding a JDBC Connector for the vRealize Orchestrator SQL Plug-In.
Deploying the VMware vRealize Orchestrator 8.1 Appliance
The vRealize Orchestrator Appliance is VMware PhotonOS-based appliance distributed as an OVA file. It is prebuilt and preconfigured with an internal PostgreSQL database, and it can be deployed with vCenter Server 6.0 or later.
The vRealize Orchestrator Appliance is a fast, easy to use, and more affordable way to integrate the VMware cloud stack, including vRealize Automation and vCenter Server, with your IT processes and environment.
For instructions about deploying the vRealize Orchestrator Appliance, see Download and Deploy the vRealize Orchestrator Appliance.
For information about configuring the vRealize Orchestrator Appliance server, see Configuring a Standalone vRealize Orchestrator Server.
Upgrading and Migrating to vRealize Orchestrator 8.1
You can upgrade a standalone or clustered vRealize Orchestrator 8.0 or 8.0.1 deployment to the latest product version by using a mounted ISO image.
For more information about upgrading the vRealize Orchestrator Appliance, see Upgrading vRealize Orchestrator.
You can migrate a standalone vRealize Orchestrator 7.3 to 7.6 instance authenticated with vSphere to vRealize Orchestrator 8.1. The migration of clustered vRealize Orchestrator 7.x deployments or deployments authenticated with vRealize Automation is not supported.
For more information about migrating the vRealize Orchestrator Appliance, see Migrating vRealize Orchestrator.
Root Password Expiry Extension
Important: For security reasons, the password expiry of the root account of the vRealize Orchestrator Appliance is set to 365 days. To increase the expiry time for an account, log in to the vRealize Orchestrator Appliance as root, and run the following command:
passwd -x number_of_days name_of_account
To make your vRealize Orchestrator Appliance root password last forever, run the following command:
passwd -x 99999 root
Plug-Ins Installed with vRealize Orchestrator 8.1
The following plug-ins are installed by default with vRealize Orchestrator 8.1
- vRealize Orchestrator vCenter Server Plug-In 6.5.0
- vRealize Orchestrator Mail Plug-In 7.0.1
- vRealize Orchestrator SQL Plug-In 1.1.4
- vRealize Orchestrator SSH Plug-In 7.1.1
- vRealize Orchestrator SOAP Plug-In 2.0.1
- vRealize Orchestrator HTTP-REST Plug-In 2.3.5
- vRealize Orchestrator Plug-In for Microsoft Active Directory 3.0.10
- vRealize Orchestrator AMQP Plug-In 1.0.4
- vRealize Orchestrator SNMP Plug-In 1.0.3
- vRealize Orchestrator PowerShell Plug-In 1.0.14
- vRealize Orchestrator Multi-Node Plug-In 8.1.0
- vRealize Orchestrator Dynamic Types 1.3.5
- vRealize Orchestrator vCloud Suite API (vAPI) Plug-In 7.5.1
vRealize Orchestrator 8.1 provides multi-language support for the vRealize Orchestrator Control Center and the vRealize Orchestrator Client.
How to Provide Feedback
Your active feedback is appreciated. Provide your feedback by using one of the following methods:
- Support Requests (SRs)
- The vRealize Orchestrator Community Forum
File all issues that you find as Support Requests (SRs), even if you report them to VMware by other means.
For more information on VMware Support and instructions on how to file SRs, please visit the official VMware Support Offerings page.
Include log files in your SRs.
To generate your vRealize Orchestrator logs:
1. Log in to the vRealize Orchestrator Appliance command line as root.
2. Run the vracli log-bundle command.
Result: The log bundle is generated in the root folder of the vRealize Orchestrator Appliance.
Earlier Releases of vRealize Orchestrator
Features and issues from earlier releases of vRealize Orchestrator are described in the release notes for each release. To review release notes for earlier releases of vRealize Orchestrator, click one of the following links:
- vRealize Orchestrator 8.0.1
- vRealize Orchestrator 8.0
- vRealize Orchestrator 7.6.0
- vRealize Orchestrator 7.5.0
- vRealize Orchestrator 7.4.0
- Unable to validate an SSH address when configuring a GitLab integration.
Adding an SSH address and clicking on the validation button causes the following error: Error: org.bouncycastle.util.io.pem.PemGenerationException: unknown object passed - can't encode.
Workaround: When you add an SSH address, you must first click on the Save button to generate a public key. Paste your public key and add it in GitLab, so you can connect to your repository.
- After migrating vRealize Orchestrator 7.x to 8.0.1, Active Directory takes a long time to show all plug-in folders in the inventory.
This issue is not consistently observed, but in rare cases after migration the Active Directory inventory does not appear immediately in the vRealize Orchestrator Client.
No workaround. Wait for the problem to resolve itself.
- Workflow Designers cannot run policies created by them in the vRealize Orchestrator Client.
After creating a policy, the Workflow Designer clicks Run. Navigating to the Policy Runs page shows that the policy run initiated by the Workflow Designer is in the Stopped state.
Workaround: Have a user with administrator rights run the policy created by the Workflow Designer.
- Receiving a 401 Unautherized Error after joining a single node to a vRealize Orchestrator High Availability (HA) environment.
After joining a node to a vRealize Orchestrator HA environment, you receive a 401 error when trying to access the vRealize Orchestrator Client. This error only appears if the vRealize Orchestrator node is authenticated with vRealize Automation.
Workaround: Reconfigure your authentication provider settings in the Control Center. Unregister the vRealize Automation authentication provider and register it again.
- Increasing the size of vRealize Orchestrator Appliance disks is not reflected on the Operating System (OS) level.
After increasing the size of any of the discs of a vRealize Orchestrator 8.0.1 Appliance, the changes are not reflected in the OS. New disc space is not accessible even after auto resize is triggered manually with the vracli disk-mgr resize command
Follow the KB https://kb.vmware.com/kb/76933
The known issues are grouped as follows.
- Configuration Issues
- Migration/Upgrade issues
- Web client
- Miscellaneous Issues
- Previously known issues
- The vRealize Orchestrator Control Center container fails to start and cannot be opened in the browser.
This issue is caused by an error in the in /data/vco/usr/lib/vco/configuration/log/catalina.log file.
1. Restart the vco-app pod that got stuck by performing the following command:
kubectl -n prelude delete pod vco-app[id]
2. After a few seconds, the pod is destroyed and a new pod is deployed.
* vco-app-[id_new_deployment] 3/3 Running 30 4d6h
- Duplicated folders appear in Tree View in an embedded vRealize Orchestrator Client after upgrading a High Availability (HA) vRealize Automation 8.0.1 environment.
After upgrading to vRealize Automation 8.1, multiple folders with identical names appear in the Tree View of the embedded vRealize Orchesreator Client. One of the folders is used while the other folders might be empty. A similar issue can also occur with fresh HA vRealize Automation 8.1 deployments.
See KB 78958.
- Failure when pushing commits to a protected Git branch.
If the configured Git branch is protected, the push operation fails consistently, but the received message indicates that the push is successful.
- Unable to load more than 20 object cards from Card View.
If you configure your display to use a 2K resolution and above, or a custom resolution that is more than 1080 pixels in height, the Card View cannot load more than 20 cards.
Configure your display to the 1920×1080 resolution at the highest. Alternatively, if you want to use other resolutions, resize the browser window, so a scrollbar appears.
- Missing Duplicate button in Tree View.
In Tree View, when selecting folders or individual objects, there is a missing duplicate button.
If you must duplicate items or folders, switch to the Card View and select Duplicate from the actions menu.
- Workflow validation errors persist for workflows even after resolving the errors.
Validation errors do not disappear from the workflow schema after resolving the errors and saving the validated workflow.
- Pull and push operations take a long time to finish.
In some cases, pull and push operations from the vRealize Orchestrator Client to the integrated Git server continue for 2 minutes.
No workaround. Wait for the pull or push operation to finish.
- Executing a workflow with a legacy presentation validation always fails when the ognl uses the "__current" variable.
Workflows created in the Orchestrator Legacy Client that use the "__current" variable in their OGNL custom validation script fail to start from the vRealize Orchestrator Client when the field value is an sdk object.
Replace the "__current" variable with the actual variable name in the workflow XML.
- Receiving errors when running custom decision element script with the new runtimes.
Do not add custom decision scripts to Python, Node.js, or PowerShell scripts.
- Users can discard Git changes to content they do not have access to.
Users with workflow designer rights can discard Git changes to content they do not have access to from the Git History page.
- Policy templates and configuration elements from plug-ins are unlocked and can be edited.
Plug-in specific policy templates and configuration elements are unlocked, and the user can edit the objects without duplicating them.
- Properties and Array/Properties types cannot have default external source values.
Using external values for Properties and Array/Properties types in the workflow input form does not show the correct actions. Even if you are able to set the correct action, the input form is populated with invalid values during validation.
Use Composite Type input parameters.
- Preinstalled actions cannot be duplicated.
If you edit actions that come with the standard vRealize Orchestrator library, you must first duplicate the relevant action. You are unable to duplicate the action because the Duplicate button is missing from the action card.
Create an empty action with same inputs parameters, return type, and script.
- Breakpoints are enabled in visual diff view in Version History.
The user can place element and scriptable task breakpoints in the visual diff view.
Do not place breakpoints in the visual diff view, as they are not supported for use in that view.
- In the vRealize Orchestrator Client, you see tags containing underscore characters in the name.
The vRealize Orchestrator Client does not support tag names with less than three characters or names containing white-space characters. All tags auto-generated from objects with shorter names will be suffixed with "underscore". All white-space characters will also be replaced with "underscore".
Example: The workflow located in "/Library/project A/app/DR/backup" in the Orchestrator Legacy Client, will have the following auto-generated tags in the vRealize Orchestrator Client: "Library", "project_A", "app", "DR_"
Workaround: Follow the presented tagging conventions when creating new content in the vRealize Orchestrator Client.
- The Version History page displays inaccurate data for the current version. After performing a push operation, the last change made to the content disappears.
This error can occur when multiple object editors are open at the same time and one or more users are making changes. For example, a user might make changes to a vRealize Orchestrator workflow and a vRealize Orchestrator action in separate tabs in their browser. After several changes to both the workflow and the action, the user saves their changes. After saving the changes to the workflow, the user pushes the updated workflow to the integrated Git repository. After pushing the workflow changes to the Git repository, the previously saved changes to the action are lost.
Reopen editors after pushing or pulling content to and from your Git repository. If there are local changes not made by you, do not push from the Git History page. Check if your local changes match the last changes to the content before pushing.
- The vCenter Server plug-in does not support policies.
The vCenter Server plug-in for vRealize Orchestrator does not support using policies to monitor for events that are issued by the managed vCenter Server instance.
- Importing a package created in a newer vRealize Orchestrator version into an older version of vRealize Orchestrator can cause an error.
Compatibility issues between vRealize Orchestrator versions lead to the inability to import packages created in newer product versions into older vRealize Orchestrator deployments.
- During the installation of a plug-in in Control Center, an error message appears.
When you install a plug-in from the
Manage Plug-Inspage in Control Center, the error message
Plug-in 'name_of_the_plug-in' (plug-in_file_name) is not compatible with the current platform version. Supported platform versions are ''. Clicking on the 'Install' button will install it anywayappears. You can safely ignore this error and proceed with the installation of the plug-in.
The Orchestrator authentication configuration might become invalid, if the authentication provider certificate changes or regenerates.
When the SSL certificate of the vRealize Automation or vSphere instance that is configured as the authentication provider in Control Center is changed or regenerated, the Orchestrator authentication configuration becomes invalid and the Orchestrator server cannot start.
Workaround: Import the new authentication provider certificate:
- Log in to Control Center as root.
- Click Certificates.
- Click the Import on the Trusted Certificates tab.
- Load the SSL certificate from a URL or a file.
- Click Import.
- The SOAP plug-in cannot connect through an authenticated proxy server.
When you run the
Add a SOAP hostworkflow, use a proxy server that does not require authentication.
If you experience issues connecting to a SOAP or a REST host, or importing a certificate, you might have to explicitly enable certain versions of SSL or TLS.
For information about this issue, see https://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html.
Workaround: For information about explicitly enabling SSLv3 and TLSv1 for outgoing HTTPS connections, see Enable TLSv1 for outgoing HTTPS connections in vRealize Orchestrator 6.0.4 and 7.0.x manually (KB 2144318).
- vCenter Server objects are not accessible in the vSphere Web Client (Flex)
Orchestrator cannot access vCenter Server objects in the vSphere Web Client (Flex), if the vCenter Server instance that you are attempting to access is registered in Orchestrator by IP address.
Workaround: Register the vCenter Server instance by host name.
- The SSH plug-in cannot connect to a Cisco Adaptive Security Appliance (ASA) firewall.
The SSH plug-in for vRealize Orchestrator 7.1 does not support connectivity to a Cisco Adaptive Security Appliance (ASA) firewall.
- Problems handling non-ASCII characters in certain contexts.
Using non-ASCII characters in input parameters results in incorrect behavior in the following situations:
- If you run the SCP put or SCP get workflows from the SSH folder on a file with a name that contains non-ASCII characters, the workflow runs, but name of the resulting file on the destination machine is unreadable.
- If you try to insert non-ASCII characters into attribute names, the characters do not appear. This issue occurs for workflow attributes and action attributes.
- The Storage VSAN workflows of the vCenter Server plug-in do not support adding Solid-State Drive (SSD) disks to an ESXi host.
Add disks to disk groupand
Remove disks from disk groupsworkflows do not support adding SSD disks as capacity disks to ESXi hosts.
Compiling a custom model-driven plug-in fails if you use an extension method that contains lambda expressions.
When you use model-driven to create plug-ins and you add extension methods to a certain extension, the plug-in does not compile if the extension method contains lambda expressions. The plug-in compilation fails with an error message, similar to the following:
Caused by: java.lang.ArrayIndexOutOfBoundsException: 52789.
Workaround: Do not use lambda expressions in the body of the extension methods.
- The RESTOperation ID does not initialize properly if the REST host instance is created by using a Swagger spec.
In the HTTP-REST plug-in, when the REST host instance is created by a Swagger spec, the RESTOperation ID does not initialize properly and the getOperation of the RESTHost object does not work.
The Convert disks to thin provisioning workflow does not handle virtual machines with snapshots correctly and does not convert the thick-provisioned disks.
On completion, the Convert disks to thin provisioning workflow reports that the thick-provisioned disks of virtual machines with snapshots are successfully converted to thin-provisioned, but they are not.
Workaround: Do not include virtual machines with snapshots in the workflow.
- Adding values to vCenter Server data object properties of the Array type is not possible.
For example, the following code does not work:
var spec = new VcVirtualMachineConfigSpec();
spec.deviceChange = ;
spec.deviceChange = new VcVirtualDeviceConfigSpec();
In the above code, Orchestrator converts the empty
VirtualDeviceConfigSpecbefore it calls
setDeviceChange(). When calling
spec.deviceChange = new VcVirtualDeviceConfigSpec(), Orchestrator calls
getDeviceChange()and the array remains a fixed, empty Java array. Calling s
pec.deviceChange.add()results in the same behavior.
Workaround: Declare the array as a local variable:
var spec = new VcVirtualMachineConfigSpec();
var deviceSpec = ;
deviceSpec = new VcVirtualDeviceConfigSpec();
spec.deviceChange = deviceSpec;
- Passing a VcSnapshotInfo object as an attribute of type Any between two workflow elements causes an exception during serialization
In the vCenter Server plug-in, passing a
VcSnapshotInfoobject or an array of
VcSnapshotInfoobjects as an attribute of type
Anybetween two workflow elements triggers a serialization that fails with a
Can not set long field com.codahale.metrics.error message.
Workaround: Change the workflow to omit passing a
VcSnapshotInfoobject or an array of
VcSnapshotInfoobjects between the workflow elements.