VMware vCenter Orchestrator 5.1.3.1 Release Notes
vCenter Orchestrator Appliance 5.1.3.1 | 30 April 2015 | Build 2689905
Check frequently for additions and updates to these release notes.
|
What's in the Release Notes
The release notes cover the following topics:
What's New in vCenter Orchestrator 5.1.3.1
vRealize Orchestrator 5.1.3.1 is a patch release that resolves an important issue. See Resolved Issues.
Downloading and Installing VMware vCenter Orchestrator 5.1.3.1
You can install Orchestrator 5.1.3.1 only on 64-bit operating system platform. If you have downloaded and installed VMware vCenter Server 5.1 Update 3, Orchestrator is already installed on your system and needs no further configuration.
Read Installing and Configuring VMware vCenter Orchestrator for step-by-step guidance on configuring vCenter Orchestrator.
Upgrading to vCenter Orchestrator 5.1.3.1 and Migrating the Orchestrator Configuration Data
To upgrade an installation of Orchestrator 4.2 on a 64-bit Microsoft Windows server that is different from the server on which vCenter Server runs, run the latest version of the Orchestrator standalone installer.
If vCenter Orchestrator 4.0.x is installed on the same 64-bit machine as vCenter Server 4.0.x, you cannot upgrade to Orchestrator 5.1.3.1 by upgrading to vCenter Server 5.1.3. VMware does not support the in-place upgrade of a standalone Orchestrator instance running on a 64-bit machine. To upgrade to vCenter Orchestrator 5.1.3.1, you must export the Orchestrator configuration settings, uninstall the existing Orchestrator instance, run the 64-bit Orchestrator installer, and import the configuration settings.
Read Installing and Configuring VMware vCenter Orchestrator for step-by-step guidance on migrating the Orchestrator configuration settings.
If you have developed workflows, actions, plug-ins, policies, and so on, by using a previous version of Orchestrator, perform the following steps:
- Export packages of all the custom workflows, actions, policies, and so on, that you developed with the earlier version of Orchestrator.
- Create a new instance of an empty database for Orchestrator 5.1.3.1.
- Install and Configure Orchestrator 5.1.3.1 by following the instructions in the Installing and Configuring VMware vCenter Orchestrator documentation.
- Connect Orchestrator 5.1.3.1 to the new Orchestrator database.
- Import the packages you exported from the older version of Orchestrator.
Top of Page
Internationalization (I18N) Support
vCenter Orchestrator 5.1.3.1 complies with I18N Level 1. Although Orchestrator is not localized, it can run on non-English operating systems and handle non-English text.
How to Provide Feedback
Your active feedback is appreciated. Provide your feedback by:
- Support Requests (SRs)
- Orchestrator Discussion Forum
Support Requests
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 http://www.vmware.com/support/services/.
Experienced SR users can file support requests at http://www.vmware.com/support/sr/sr_login.jsp.
Use your registered VMware store account to log in.
Include log files in your SRs. To gather log files from Orchestrator:
- Go to the Orchestrator configuration interface at
https://orchestrator_server_ip_address:8283.
- Log in with your username and password.
- Click Logs.
- Click Generate log report.
- Save the generated ZIP file.
- Upload the saved ZIP file to VMware Support.
For Orchestrator configuration issues, include an exported configuration file in your SRs. To export your configuration from the Orchestrator configuration interface:
- Go to the Orchestrator configuration interface at
https://orchestrator_server_ip_address:8283.
- Log in with your username and password.
- Click General.
- Click the Export Configuration tab.
- (Optional) Type your password and press Enter.
- Save the
*.vmoconfig file.
- Upload the saved files to VMware Support.
Orchestrator Discussion Forum
View the Orchestrator forum at http://communities.vmware.com/community/vmtn/mgmt/orchestrator. Use your registered VMware store account to log in.
Top of Page
Earlier Releases of vCenter Orchestrator
Features and issues from earlier releases of vCenter Orchestrator are described in the release notes for each release. To review release notes for earlier releases of vCenter Orchestrator, click one of the following links:
Resolved Issues
The Oracle (Sun) JRE package is updated to 1.7.0_76. The update addresses multiple security issues that exist in the earlier releases of Oracle (Sun) JRE. Oracle has documented the CVE identifiers that are addressed in JRE 1.7.0_76 in the Oracle Java SE Critical Patch Update Advisory for January 2015. For details, see vCenter Orchestrator and vRealize Orchestrator JRE update to include a fix for CVE-2014-6593 (KB 2112028).
Top of Page
Known Issues
The known issues are grouped as follows:
Installation and Upgrade Issues
- The Orchestrator client cannot be started if it was running when upgrading to vCenter Orchestrator 5.1.3.1
If you have an instance of the Orchestrator client running on the same machine where the Orchestrator server is installed and you perform an upgrade to Orchestrator 5.1.3.1, the Orchestrator client cannot be stopped after the upgrade and you must stop the process manually. After you restart the machine, the Orchestrator client cannot be started again.
- Restarting vCO server service after reinstalling plug-ins adds Java exceptions to the logs
In the Troubleshooting tab of the Orchestrator configuration interface, if you reinstall plug-ins by clicking Reset current version and then restart the Orchestrator server, several Java exceptions are written to the Orchestrator server logs.
- You cannot upgrade Orchestrator during a vCenter Server upgrade
You cannot upgrade Orchestrator 4.2 to version 5.1.3.1 during the upgrade of vCenter Server.
Workaround: To upgrade Orchestrator 4.2 to Orchestrator 5.1.3.1, start the standalone vCenter Orchestrator installer and upgrade Orchestrator. To start the standalone installer, in the software installer directory, browse to the C:\install_directory\vCenter-Server\vCO\ folder and double-click vCenterOrchestrator.exe.
Internationalization Issues
- You might not be able to configure the LDAP settings if your LDAP password contains non-ASCII characters
When you try to configure the LDAP settings in the Orchestrator configuration interface and the LDAP password that you enter contains non-ASCII characters, the process of configuring might fail with an error message of the type Unable to connect to LDAP Server. This issue appears under the following conditions:
- When the LDAP password contains characters such as € and ÿ in German and French locales.
- When the LDAP password contains any native characters in Japanese, Korean, and Simplified Chinese locales.
- Problems handling non-ASCII characters in certain contexts
Using non-ASCII characters in input parameters results in incorrect behavior in the following contexts:
- 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 garbled.
- If you try to insert non-ASCII characters into attribute names, the characters do not appear. The issue occurs for Web view attributes, workflow attributes and action attributes.
Configuration Issues
- vCenter Orchestrator 5.1.3.1 does not support Oracle Database 12c
The Orchestrator server cannot start when it is configured to use Oracle Database 12c.
- Orchestrator does not work with forest and external trusts in Active Directory
Multiple domains that are not in the same tree but have a two-way trust, are not supported and do not work with Orchestrator. The only configuration supported for multi-domain Active Directory is domain tree. Forest and external trusts are unsupported.
Networking Issues
Client Issues
Miscellaneous Issues
- Web views does not support multiple level of presentation field binding
Web views does not support multiple levels of presentation field binding. For example, suppose the presentation consists of the following fields and bindings:
- sourceField
- aField bound to sourceField by using a DefaultValue attribute
- bField bound to aField by using a DefaultValue attribute
When you change the value of sourceField, the value of aField is also updated, but the value of bField remains the same.
- 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, when they are actually not.
Workaround: Do not include virtual machines with snapshots in the workflow.
- Windows Server 2008 automatically renames VMOAPP and DAR files to ZIP causing the application installation and plug-in upload in the Orchestrator configuration interface to fail
If you are running Orchestrator on Windows Server 2008, the extension of the archives you download is automatically changed to ZIP. When you are installing an application or uploading a plug-in by using the Orchestrator configuration interface, you must use a VMOAPP or DAR file.
Workaround: Change the ZIP extension back to either VMOAPP or DAR to use the downloaded archive in the Orchestrator configuration interface.
- Repeatedly publishing and unpublishing Web views can cause memory issues
Publishing and unpublishing of Web views restarts the Tapestry framework, which regenerates new meta-class information without cleaning up the previous meta-class information. Publishing and unpublishing a Web view by repeatedly calling the methods Webview.enable() and Webview.disable() in a loop in scripts can consume large quantities of memory and eventually leads to performance issues.
- Adding values to vCenter Server data object properties of type Array is impossible
When Orchestrator runs scripts, the vCenter Server plug-in converts JavaScript arrays to Java arrays of a fixed size. As a consequence, you cannot add new values to vCenter Server data objects that take arrays as property values. You can create an object that takes an array as a property if you instantiate that object by passing it a pre-filled array. However, after you have instantiated the object, you cannot add values to the array.
For example, the following code does not work:
var spec = new VcVirtualMachineConfigSpec();
spec.deviceChange = [];
spec.deviceChange[0] = new VcVirtualDeviceConfigSpec();
System.log(spec.deviceChange[0]);
In the above code, Orchestrator converts the empty spec.deviceChange JavaScript array into the fixed-size Java array VirtualDeviceConfigSpec[] before it calls setDeviceChange(). When calling spec.deviceChange[0] = new VcVirtualDeviceConfigSpec(), Orchestrator calls getDeviceChange() and the array remains a fixed, empty Java array. Calling spec.deviceChange.add() results in the same behavior.
Workaround: Declare the array as a local variable, as follows:
var spec = new VcVirtualMachineConfigSpec();
var deviceSpec = [];
deviceSpec[0] = new VcVirtualDeviceConfigSpec();
spec.deviceChange = deviceSpec;
System.log(spec.deviceChange[0]);
- Workflow input parameters of type SecureString cannot take a null value
You cannot start a workflow with a null value if that workflow takes a SecureString as an input parameter, unless you start the workflow from within another workflow. If you start a workflow with a null value when that workflow takes a SecureString as an input parameter, the server loads attributes from the cache rather than from the Orchestrator database, resulting in a null input parameter. If you then change the workflow state to passive by implementing a long-running workflow element, the attributes are reloaded from the database, converting the null value into an empty string. This is the only way you can use a null value to start a workflow that requires a SecureString input parameter.
Top of Page
|