vRealize Orchestrator Appliance 7.3.1 | 15 March 2017 | Build 8002898
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 7.3.1
- Feature and Support Notice
- Deploying the VMware vRealize Orchestrator Appliance 7.3.1
- Internationalization Support
- How to Provide Feedback
- Prior Releases of vRealize Orchestrator
- Resolved Issues
- Known Issues
What's New in vRealize Orchestrator 7.3.1
vRealize Orchestrator 7.3.1 introduces a number of improvements, bug fixes, and extends the automated configuration with new options:
A new property is added to the SSHSession scripting object to set a socket timeout when establishing sessions.
Added 2 new workflows to support SSH with key pair:
Change a key pair pass-phrase
Generate key pair to connect to an SSH host without a password
Added support for RTIC 2018 Q1 - vAPI 2.7.0 SDK in vAPI plug-in.
Added support for Parallel HTTP Request Execution
Adding option that enables separate HTTP context per request execution.
The parallel request execution is at REST Host instance.
Once the REST host is created, its state is immutable per lifetime of the object.
Radio button at "Add a Rest Host" workflow is displayed to govern the REST host parallel feature.
Added client-side load balancing and fail-over capabilities to the Active Directory plug-in
Feature and Support Notice
- The following feature has reached its End of Life and is no longer available or supported in vRealize Orchestrator.
- LDAP authentication
- The following features are deprecated in vRealize Orchestrator and are scheduled for removal in future releases.
- Support for Microsoft SQL Server and Oracle Database as external database servers.
- Support for SNMPv3.
- The vCenter Single Sign-On Legacy authentication mode has been replaced by the vSphere authentication method.
- The following workflows of the vRealize Automation plug-in are deprecated and will not work with vRealize Automation plug-in 7.3.1.
- Create a Management Endpoint
- Delete a Management Endpoint
- Delete a Connection Credential
- Create a Connection Credential
Deploying the VMware vRealize Orchestrator Appliance 7.3.1
VMware vRealize Orchestrator 7.3.1 is available as a preconfigured virtual appliance.
The Orchestrator Appliance is distributed as an OVA file. It is prebuilt and preconfigured with Novell SUSE Linux Enterprise Server, PostgreSQL, and it can be deployed with vCenter Server 5.5 and later.
The 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.
Upgrading to vRealize Orchestrator 7.3.1
For instructions about deploying and using the Orchestrator Appliance, see Upgrading and Migrating VMware vRealize Orchestrator.
NOTE: Upgrading vRealize Orchestrator Appliance from version 5.5.x to 7.3.1 is not supported. You must upgrade your vRealize Orchestrator Appliance 5.5.x to 6.0.x first.
Important: For security reasons, the password expiry of the root account of the Orchestrator Appliance is set to 365 days. To increase the expiry time for an account, log in to the Orchestrator Appliance as root, and run the following command:
passwd -x number_of_days name_of_account
To make your Orchestrator Appliance root password last forever, run the following command:
passwd -x 99999 root
Plug-Ins Installed with vRealize Orchestrator 7.3.1
The following plug-ins are installed by default with vRealize Orchestrator 7.3.1:
- vRealize Automation Center Infrastructure Administration Plug-In 7.3.1
- vRealize Automation Plug-In 7.3.1
- vRealize Orchestrator Mail Plug-In 7.0.1
- vRealize Orchestrator SQL Plug-In 1.1.4
- vRealize Orchestrator SSH Plug-In 7.0.2
- vRealize Orchestrator SOAP Plug-In 2.0.0
- vRealize Orchestrator HTTP-REST Plug-In 2.2.2
- vRealize Orchestrator Plug-In for Microsoft Active Directory 3.0.7
- vRealize Orchestrator AMQP Plug-In 1.0.4
- vRealize Orchestrator SNMP Plug-In 1.0.3
- vRealize Orchestrator PowerShell Plug-In 1.0.12
- vRealize Orchestrator Multi-Node Plug-In 7.3.0
- vRealize Orchestrator Dynamic Types 1.3.0
- vRealize Orchestrator vCloud Suite API (vAPI) Plug-In 7.3.0
- vRealize Orchestrator Plug-In for vRealize Automation 7.3.0
For information on the changes in the vCenter Server plug-in for vRealize Orchestrator 7.3.1 and potential compatibility issues with earlier versions of the plug-in, see What's New in the New vCenter Server Plug-In.
vRealize Orchestrator 7.3.1 provides a multi-language support for Control Center and supports internationalization level 1 for the Orchestrator client.
How to Provide Feedback
Your active feedback is appreciated. Provide your feedback by using one of the following methods:
- Support Requests (SRs)
- Orchestrator Discussion Forum
File all issues that you find as Support Requests (SRs), even if you report them to VMware by other means.
You can find the VMware Support's commitment to SRs filed by customers and instructions on how to file an SR at https://www.vmware.com/support/services/beta.
Include log files in your SRs. Follow the steps to gather log files and configuration from Orchestrator:
- Go to Control Center at
- Log in as an administrator.
- Click Export Logs.
- Click Export logs.
- Save the generated ZIP file.
- Upload the saved ZIP file to VMware Support.
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 7.3.0
- vRealize Orchestrator 7.2.0
- vRealize Orchestrator 7.1.0
- vRealize Orchestrator 7.0.1
- vRealize Orchestrator 7.0
- vRealize Orchestrator 6.0.4
- vRealize Orchestrator 6.0.3
- vRealize Orchestrator 6.0.2
- vRealize Orchestrator 6.0.1
- vCenter Orchestrator 184.108.40.206
- vCenter Orchestrator 5.5.2
- vCenter Orchestrator 5.5.1
- vCenter Orchestrator 5.5
- vCenter Orchestrator 220.127.116.11
- vCenter Orchestrator 5.1.3
- vCenter Orchestrator 5.1.2
- vCenter Orchestrator 5.1.1
- vCenter Orchestrator 5.1
- vCenter Orchestrator 4.2.2
- vCenter Orchestrator 4.2.1
- vCenter Orchestrator 4.2
- vCenter Orchestrator 4.1.3
- vCenter Orchestrator 4.1.2
- vCenter Orchestrator 4.1.1
- vCenter Orchestrator 4.1
- vCenter Orchestrator 4.0.4
- vCenter Orchestrator 4.0.3
- vCenter Orchestrator 4.0.2
- vCenter Orchestrator 4.0.1
- vCenter Orchestrator 4.0
- Workflows that initiate a SOAP operation fail after an Orchestrator server restart
If you run a workflow that initiates a SOAP operation and the Orchestrator server restarts, the workflow will fail with an error similar to: Workflow:Invoke a SOAP operation / Prepare Parameters (item0) : ch.dunes.model.type.ConvertorException: Cannot convert to object , reason : Unable to perform operation 'find('Operation', '37c85322-ad52-45eb-84e3-ac91ad155dc3:Feedback')' on plugin 'SOAP' reason : 'Trying to put already available object'
- You get an Error 400! error while configuring vSphere Authentication in vRealize Orchestrator
When you configure vSphere authentication in vRealize Orchestrator, you see an error similar to: Error 400!Exception occurred. Details: Could not read document:
Unexpected token (FIELD_NAME), expected END_OBJECT: expected closing END_OBJECT after type information and deserialized value at [Source: java.io.PushbackInputStream@16ebe97d; line: 1, column: 445]; nested exception is com.fasterxml.jackson.databind.JsonMappingException: Unexpected token (FIELD_NAME), expected END_OBJECT: expected closing END_OBJECT after type information and deserialized value at [Source: java.io.PushbackInputStream@16ebe97d; line: 1, column: 445]
- Updating a preserved value in a configuration element results in an error
If you are updating a preserved value in a configuration element in the Java client, you receive the following error: java.lang.IllegalArgumentException: Comparison method violates its general contract!
- On logging in Control Center, you get a timeout error when vSphere authentication is used
If Orchestrator is authenticated with vSphere and a user belongs to a lot of user groups, a timeout error occurs when logging in to Control Center.
- Nested workflows fail with error: java.lang.IllegalArgumentException: [class/interface] is not visible from class loader
Nested workflows fail with error: java.lang.IllegalArgumentException: [class/interface] is not visible from class loader
- After defining an attribute composite type in a workflow in the Java client, you are unable to edit that composite type.
After defining an attribute composite type in a workflow in the Java client, you are unable to edit that composite type.
- Workflow runs, policies, or tasks fail with error: Unable to authenticate with OAuthToken
Workflow runs, policies, or tasks fail with error: Unable to authenticate with OAuthToken
- You might not be able to log in to Control Center if you are using a different letter case when you are authenticating with your user, group, or tenant.
You might not be able to log in to Control Center if you are using a different letter case when you are authenticating with your user, group, or tenant.
- A package export does not preserve SecureString values in a Configuration element
When you import previously exported packages, the SecureString values in the Configuration elements are empty. Workflows that depend on them will fail.
- User interaction with boolean input parameter cannot be set to No.
User interaction with boolean input parameter, which is an attribute in the workflow with a default value set to true and without a decorator cannot be set to No.
- Dynamic types definitions are lost after a cluster synchronization.
After a cluster synchronization, some of the nodes might have configured types and relations missing.
- The PowerShell plug-in fails to connect to Windows Server 2012, because of a limitation of a maximum line length when running CMD
The PowerShell plug-in fails to connect to Windows Server 2012, because of a limitation of a maximum line length when running CMD
- You receive errors when browsing the vCenter Server plug-in inventory, if you have permissions on a subset of vSphere Inventory folders
If you have permissions on a subset of vSphere Inventory folders, you are not able to browse the vCenter Server inventory.
- If you pass the VirtualEthernetCard object between workflow elements, the workflow run might fail.
This issue is observed when more than one user are running the same workflow simultaneously against a vCenter Server instance, registered in a shared session mode
- The 'Convert independent disks' workflow in the vCenter Server plug-in does not convert a disk to dependent
The Convert independent disks workflow in the vCenter Server plug-in does not convert a disk to dependent.
- There is a monitoring thread leakage, if the vAPI client is not explicitly closed
There is a monitoring thread leakage if the vAPI client is not explicitly closed. The example workflows are updated to show you the correct way of using the vAPI client.
- AMQP plug-in fails when a large number of messages must be processed
The AMQP plug-in cannot process a large number of messages at once and fails. This issue has been fixed by dropping messages when the queue gets too big and the plug-in is about to fail.
- NEW! After upgrading from vRealize Orchestrator 7.3 to 7.3.1, the hostname or network configuration such as IP address changes when the appliance is rebooted.
When upgrading vRealize Orchestrator 7.3 to 7.3.1, if you've changed the hostname, IP address or any other network configuration after deploying the vRealize Orchestrator 7.3 OVF, the upgrade process reverts vRealize Orchestrator to its initial hostname and network settings that were defined during OVF deployment.
After upgrading from vRealize Orchestrator 7.3 to 7.3.1, delete the "/opt/vmware/etc/vami/flags/vami_setnetwork" file before rebooting the vRealize Orchestrator appliance.