VMware vCenter Orchestrator 5.5.3 Release Notes

|

vCenter Orchestrator 5.5.3 | 16 September 2015 | Build 2945834

vCenter Orchestrator Appliance 5.5.3 | 12 April 2016 | Build 3696314

Release Notes last updated on 12 April 2016.

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.5.3

vCenter Orchestrator 5.5.3 is an update release resolving important issues described in Resolved Issues section. vCenter Orchestrator cluster nodes are now more tolerant to sporadic database failure. A retry logic is implemented so the servers nodes do not shut down after a single database failure. Instead the nodes try to connect to the database a configured number of times.

vCenter Orchestrator 5.5.3 Feature and Support Notice

The use of OGNL expressions in workflow presentations is supported.

The features listed below are deprecated in vCenter Orchestrator 5.5.3 and scheduled for removal in future releases. None of the deprecated features should be used as part of any vCenter Orchestrator based solution.

  • LDAP authentication is deprecated.
  • The Orchestrator configuration interface is deprecated. Recommended vRealize Orchestrator configuration and plug-ins configuration should happen through vRealize Orchestrator workflows.
  • SOAP API is deprecated.
  • The Orchestrator 5.5.3 Web configuration interface does not support Internet Explorer 8 and 9. To use the Orchestrator configuration interface, use Internet Explorer 10 or later.

Installing VMware vCenter Orchestrator 5.5.3

You can download the vCenter Server 5.5.3 installer and install Orchestrator together with vCenter Server or standalone.

Read Installing and Configuring VMware vCenter Orchestrator, the up-to-date documentation for vCenter Orchestrator 5.5.2 and 5.5.3 for step-by-step guidance on installing and configuring vCenter Orchestrator.

Upgrading to vCenter Orchestrator 5.5.3 and Migrating the Orchestrator Configuration Data

To upgrade an installation of Orchestrator 4.2.x and later 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.5.3 by upgrading to vCenter Server 5.5 Update 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.5.3, you must export the Orchestrator configuration settings, uninstall the existing Orchestrator instance, run the 64-bit Orchestrator installer, and import the configuration settings.

Important: If you upgrade only the Orchestrator client from version 5.5.2 to 5.5.3, you will not be able to connect with this client to vCenter Orchestrator 5.5.2 servers.

Important: If you upgrade vCenter Orchestrator version, which includes SOAP plug-n version 1.0.2 or earlier, to vCenter Orchestrator 5.5.3,  you must change the SOAP connection WSDL URL to http://IP:8281/vco/vmware-vmo-webcontrol/webservice?WSDL and restart the Orchestrator Server service.

Important: Orchestrator 5.5.3 does not support Single Sign-On 1.0 when using vCenter Server 5.1. If you are upgrading Orchestrator 5.1.x that is registered with Single Sign-On to Orchestrator 5.5.3, you must register the instance with Single Sign-On 2.0 after the upgrade.

If you have developed workflows, actions, plug-ins, policies, and so on, by using a previous version of Orchestrator, perform the following steps:

  1. Export packages of all the custom workflows, actions, policies, and so on, that you developed with the earlier version of Orchestrator.
  2. Create a new instance of an empty database for Orchestrator 5.5.3.
  3. Install and configure Orchestrator 5.5.3 by following the instructions in the Installing and Configuring VMware vCenter Orchestrator documentation.
  4. Connect Orchestrator 5.5.3 to the new Orchestrator database.
  5. Import the packages you exported from the earlier version of Orchestrator.

Downloading and Deploying the VMware vCenter Orchestrator Appliance 5.5.3

VMware vCenter Orchestrator is available as a preconfigured virtual appliance. The appliance significantly reduces the time and skills required to deploy vCenter Orchestrator and provides a low-cost alternative to the traditional Windows-based installation. You can download the vCenter Orchestrator Appliance 5.5.3 from the Orchestrator Appliance download link.

The Orchestrator Appliance 5.5.3 is distributed in OVF (Open Virtual Machine Format), OVA (Open Virtualization Appliance), and VMDK (Virtual Machine Disk) formats. It is pre-built and pre-configured with Novell SUSE Linux Enterprise Server, PostgreSQL, and OpenLDAP.

The Orchestrator Appliance offers great flexibility and uncompromised performance, making it ideal for any use case from lab evaluation to large-scale production use. The appliance offers all of the components included in the regular Windows-based installation, along with the flexibility to use either the pre-built directory services and database, or external ones like Active Directory or Oracle. What's more, the Orchestrator appliance has been certified to run at the same performance level as the Windows-based installation.

The Orchestrator Appliance makes it even faster, easier, and more affordable to integrate the VMware cloud stack, including vCenter Server and vCloud Director, with your IT processes and environment.

Important: You can perform an in-place upgrade to version 5.5.3 of Orchestrator Appliance 5.5 or later. To upgrade Orchestrator Appliance 5.1.x and earlier to Orchestrator 5.5.3, you must download and deploy the latest version of the appliance, and migrate the data from a previous appliance version. For instructions about upgrading the Orchestrator Appliance, see Installing and Configuring VMware vCenter Orchestrator.

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 into the Orchestrator Appliance as root, and run:

passwd -x number_of_days name_of_account

To make your Orchestrator Appliance root password last forever, run:

passwd -x 99999 root

Plug-Ins Installed with vCenter Orchestrator 5.5.3

The following plug-ins are installed by default with vCenter Orchestrator 5.5.3:

  • vCenter Orchestrator vCenter Plug-In 5.5.3
  • vCenter Orchestrator Mail Plug-In 5.5.1
  • vCenter Orchestrator SQL Plug-In 1.1.1
  • vCenter Orchestrator SSH Plug-In 2.0.0
  • vCenter Orchestrator SOAP Plug-In 1.0.3
  • vCenter Orchestrator HTTP-REST Plug-In 1.0.3
  • vCenter Orchestrator Plug-In for Microsoft Active Directory 1.0.5
  • vCenter Orchestrator AMQP Plug-In 1.0.3
  • vCenter Orchestrator SNMP Plug-In 1.0.2
  • vCenter Orchestrator PowerShell Plug-In 1.0.4
  • vCenter Orchestrator Multi-Node Plug-In 5.5.2
  • vCenter Orchestrator Dynamic Types 1.0.0

Internationalization Support

vCenter Orchestrator 5.5.3 supports internationalization 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 over the next few weeks 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/.

Include log files in your SRs. To gather log files from Orchestrator:

  1. Go to the Orchestrator configuration interface at https://orchestrator_server_ip_address:8283.
  2. Log in with your username and password.
  3. Click Logs.
  4. Click Generate log report.
  5. Save the generated ZIP file.
  6. 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:

  1. Go to the Orchestrator configuration interface at https://orchestrator_server_ip_address:8283.
  2. Log in with your username and password.
  3. Click General.
  4. Click the Export Configuration tab.
  5. Type your password and press Enter.
  6. Save the *.vmoconfig file.
  7. Upload the saved files to VMware Support.

Orchestrator Discussion Forum

View the Orchestrator 5.5.3 forum at https://communities.vmware.com/community/vmtn/vcenter/orchestrator.

Prior 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

vCenter Orchestrator 5.5.3 resolves the following issues:

  • NEW! CVE-2015-7547 glibc getaddrinfo() stack-based buffer overflow

    The issue is resolved in this release for the vRealize Orchestrator Appliance.

  • NEW! JRE Updated

    The Oracle (Sun) JRE package is updated to 1.7.0_99. The update addresses multiple security issues that exist in the earlier releases of Oracle (Sun) JRE.
    The issue is resolved in this release for the vRealize Orchestrator Appliance.

  • Workflows might fail with an Undefined function: matches error
    If you are using the built-in xpath scripting function matches() of a vCenter Server plug-in to filter a list of virtual machines by the value of a subproperty, some of the objects might get a parent property set to null, which causes the function to throw an exception and fail the entire query with an Undefined function: matches error.

    The issue is resolved in this release.

  • Multi-Node plug-in might extract the type attribute from the incorrect location
    When generating remote plug-in objects, the Multi-Node plug-in might extract the type attribute from the incorrect location.

    The issue is resolved in this release.

  • When you use vCenter Orchestrator Multi-Node plug-in, the workflow status from the slave Orchestrator server might not be reported to the master Orchestrator server
    When you run a slave Orchestrator server workflow the result does not show in the master Orchestrator server and after several attempts, the workflow starts giving random results. If a workflow fails, every workflow after it fails too.

    The issue is resolved in this release.

  • Problematic releasing of locks
    If you create a lock with LockingSystem.lockAndWait(lockName,"") and try to release it by running the Release all locks workflow, the LockingSystem.unlockAll() method does not release all locks.

    The issue is resolved in this release.

  • Errors might occur when browsing the inventory tree in Web views
    If you are browsing the inventory tree by using Web views, you might receive an error of type RPC error: XMLHttpTransport Error: 500 Internal Server Error.

    The issue is resolved in this release.

  • Orchestrator returns a limited number of objects
    When you use Orchestrator with the vCenter Server 5.5.x plug-in, the getAllVMsOfResourcePool, getAllVMsOfCluster, and getAllVMsOfComputeResource actions show a maximum of 100 results.

    The issue is resolved in this release.

  • The Orchestrator Mail plug-in returns an Invalid Email addresses error message
    If the Mail plug-in tries to send a message to multiple email addresses and one or more of the email addresses in the list are incorrect, the message is not delivered to the correct email addresses and you receive an Invalid Email addresses error message.

    The issue is resolved in this release.

  • The SCP put command does not work as expected
    When you use the SCP put command in a workflow, the command does not fail and is successfully completed on SSH timeout.

    The issue is resolved in this release.

  • vCenter Orchestrator workflow presenation fail with Invalid or missing session ID error
    When the workflow presentation calls OGNL actions from the smart client, the workflow might fail with Invalid or missing session ID error.

    The issue is resolved in this release.

  • vCenter Orchestrator become unresponsive with OutOfMemoryException
    When you use the Multi-Node plug-in and it is disabled by default, it makes requests to the notification URL. The following error is reported in the Orchestrator log: ERROR {} [SDKModuleNotificationHandler] JMS Error : Cannot deliver object to client , reason : javax.jms.IllegalStateException: Session is closed.

    The issue is resolved in this release.

  • Importing packages on Orchestrator systems might fail
    When you export and then import a package from one Orchestrator system to the same or to another Orchestrator system, the import might fail with Unable to extract package from raw data error.

    The issue is resolved in this release.

  • Orchestrator active nodes become inactive
    Orchestrator active nodes shut down on database connection interruption and stop processing workflows run requests.

    The issue is resolved in this release by providing retrial algorithm based on cluster configuration. After retrial timeout is reached node shut down itself.

  • Cannot update vCenter Server configuration after changing the network parameters
    If you configure a vCenter Server instance and change the network parameters, you cannot update the configuration, receiving the Workflow execution failed with error: com.vmware.vim.vmomi.client.exception.ConnectionException: org.apache.http.conn.HttpHostConnectException: Connection to https://sof2-lab3-dhcp381.eng.vmware.com:443 refused error.

    The issue is resolved in this release.

  • Orchestrator disconnects from vCenter Server
    When Orchestrator disconnects from a vCenter Server instance, it is unable to reconnect until you restart the Orchestrator services.

    The issue is resolved in this release.

  • The Shut down and delete virtual machine workflow does not force the shutdown
    If you are using the Shut down and delete virtual machine workflow and the virtual machine encounters an issue during the guest OS shutdown, the workflow does not force the virtual machine to shut down.

    The issue is resolved in this release.

  • Clone, Windows with multiple NICs and credential workflow fails if User's Full Name field is empty
    If you run the Clone, Windows with multiple NICs and credential workflow and leave the User's Full Name field empty, the vCenter Server service crashes and restarts, causing the workflow to fail.

    The issue is resolved in this release.

  • The setDiskToNonPersitent action does not function
    If you use the setDiskToNonPersitent action on a virtual machine, there is no effect.

    The issue is resolved in this release by providing a new action setDisksToNonPersisten.

  • Changes to an action called by another action do not apply unless you restart the Orchestrator service
    Changes made to an action called by an action that is attached to an input parameter in a presentation do not apply in Web Views unless you restart the Orchestrator service.

    The issue is resolved in this release by adding the com.vmware.o11n.webviews.cache.enabled property. If the value is set to true, and an Orchestrator server restart is needed for the changes of an action to occur. If it is set to false, an Orchestrator server restart is not needed. The value is set to false by default

  • You might not be able to search groups when Orchestrator is configured in Single Sign-On mode
    If you try to search for a specific group or list all available groups in Orchestrator and one of the domains from the configured identity provider is not available, Orchestrator does not return any results.

    The issue is resolved in this release.

  • After upgrading, Orchestrator disconnects from the vCenter Server inventory
    After upgrading vCenter Server and Orchestrator, Orchestrator disconnects from the vCenter Server inventory.

    The issue is resolved in this release.

  • Orchestrator cannot use distributed port groups for new virtual machines
    If you upgrade the vCenter Server plug-in to 5.5.2 or later, virtual machines cannot be attached to distributed port groups, imported from a previous vCenter Server instance.

    The issue is resolved in this release.

  • If the bisness-state of a workflow contains special XML characters the workflow does not finish
    If you create a new workflow, use special XML characters in the business-state, and run the workflow, the schema gets deleted and the workflow fails.

    The issue is resolved in this release.

  • Cannot set an array of String as value in a VcKeyAnyValue instance

    The issue is resolved in this release.

  • Deleting linked cloned virtual machines, does not delete the redo logs and snapshot data connecting them to the virtual machine template
    If you delete linked cloned virtual machines, the redo logs and snapshot data that references them to the virtual machine template does not get deleted.

    The issue is resolved in this release.

  • Running workflows of the vCenter Server plug-in might freeze and not finish
    When updating values of vCenter Server plug-in object properties, the running workflows of the vCenter Server plug-in freeze and do not finish.

    The issue is resolved in this release.

  • Orchestrator performing slow
    If your Orchestrator environment has a Multi-Node plug-in configured as a master of another Orchestrator instance, you might experience performance issues such as slow workflow execution, timeouts, and problems with various Orchestrator elements.

    The issue is resolved in this release.

  • The Expand package to folder option cannot export the values of the configuration settings
    If you are using the Expand package to folder option and select Export the values of the configuration settings, the values are not exported.

    The issue is resolved in this release.

  • vCenter Server instances are listed with an invalid login error
    If you change your password for Orchestrator, the vCenter Server instances that are added as session-per-user display an invalid login error.

    The issue is resolved in this release.

  • The setDiskToNonPersitent action does not function
    If you use the setDiskToNonPersitent action on a virtual machine, there is no effect. Use the setDisksToNonPersistent action instead.

    The issue is resolved in this release.

  • Actions in a package might not be added
    If you manually create a package and add an action, the action might not be saved and cannot be added to the package.

    The issue is resolved in this release.

  • Orchestrator installer does not complete upgrading
    If you are upgrading Orchestrator 5.5.1 or earlier to version 6.0.2, without upgrading the Single Sign-On that the Orchestrator server is configured to use, the installer does not complete upgrading. All versions of Single Sign-On that work with vCenter Server 5.5 update 1 and earlier are incompatible with Orchestrator server 5.5.2 and later.

    The issue is resolved in this release.

  • vim3waitTaskend action freezes and prevents the completion of the workflow
    If you are using the vim3waitTaskend action in a workflow, it might freeze and prevent the workflow to complete.

    The issue is resolved in this release.

  • Orchestrator active nodes become inactive
    If there is a database connection failure, the Orchestrator active nodes shutdown and stop processing workflow run requests.

    This issue is resolved by providing a retrial algorithm based on cluster configuration. The Orchestrator active node will attempt to reconnect a given number of times and will shut down if the attempts are unsuccessful.

Known Issues

The known issues are grouped as follows:

Installation and Upgrade Issues

  • After upgrading vCenter Orchestrator to 5.5.3, you might not be able to log in to the Orchestrator client
    When you attempt to log in to the Orchestrator client after upgrading to vCenter Orchestrator 5.5.3, you might get an error message Invalid username/password.

    Workaround: Back up the %INSTALL_DIR%/apps/lib/bcprov-jdk15.jar file and delete it manually.

  • The installation directory of vCenter Orchestrator 5.5.3 cannot contain underscores
    If you install vCenter Orchestrator to a file path which contains '_' characters, an error is generated.

  • New log event purging strategy is not applied after upgrade
    After you deploy the Orchestrator Appliance or upgrade an existing Orchestrator installation, the new log event purging strategy is not applied and the last 5,000 log events per workflow are kept.

    Workaround: To apply the new purging strategy and configure the number of days to keep log events:

    1. Log in to the Orchestrator configuration interface.
    2. From the General tab, select Advanced Configuration.
    3. In the Expiration days of log events text box, type the number of days to keep log events and click Apply changes.
    4. Click the Startup Options tab and click Restart service.
  • Upgrading the Single Sign-On version might cause issues
    If you register Orchestrator to use Single Sign-On and subsequently upgrade the Single Sign-On version, you receive an invalid credentials error message when you try to log in to Orchestrator.

    Workaround: Perform the Single Sign-On registration again.

  • Trying to log in to the Orchestrator client during upgrade results in an error
    If you try to log in to the Orchestrator client during upgrade, you receive an Invalid username/password error message.

    Workaround: To be able to log in to the Orchestrator client:

    1. Log in to the vSphere Web Client as a user with administrative privileges for Single Sign-On.
    2. Navigate to Administration > Single Sign-On > Users and Groups and select the Groups tab.
    3. Create the ActAsUsers group if it does not exist.
    4. Add the Orchestrator application user that is a member of the vsphere.local domain and has user name vCO-<hash_code>, as a member of the ActAsUsers group.
  • If you upgrade vCenter Orchestrator 5.1.x or 5.5 with an Oracle database to Orchestrator 5.5.3, the database schema might not be updated
    When configuring the database through the Orchestrator web configuration interface, the following error is reported: Mismatch database version (found version '1.60', was expecting version '1.63'). In the Orchestrator log, you can see the following message: ORA-01450: maximum key length (6398) exceeded.

    Workaround: To prevent the error related to the Oracle database when upgrading to vCenter Orchestrator 5.5.3:

    1. Stop the Orchestrator Server service and the Orchestrator Configuration service.
    2. Upgrade vCenter Orchestrator to version 5.5.3.
    3. Run the following script against Oracle database:
      UPDATE VMO_ConfigItem set itemValue = '1.61' where id = 'item_db_version'
    4. Start the Orchestrator Configuration service and log in to Orchestrator configuration interface.
    5. Navigate to Database configuration and click Update link.
  • After upgrading to vCenter Orchestrator 5.5.3 as part of vCenter Server which is configured with an Oracle database, you might not be able to log in
    If you upgrade a vCenter Orchestrator instance which is installed as part of vCenter Server and uses a vDB database connection to the Oracle database of the vCenter Server, you might not be able to log in to the Orchestrator after the upgrade, although the Orchestrator server starts successfully. The following error is reported in the Orchestrator log: Could not establish a connection to the database. Retrying in 30s.

    Workaround:

    1. Stop the Orchestrator Server service.
    2. Start the Orchestrator Configuration service and log in to Orchestrator configuration interface.
    3. Navigate to Database configuration and change the database connection type from vDB to Oracle.
    4. Fill in the properties of the connection to the vCenter Server database.
    5. Upgrade vCenter Orchestrator to version 5.5.3.
  • Restarting Orchestrator 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.
  • Orchestrator registry keys remain after you uninstall Orchestrator by using Windows Control Panel
    If you uninstall Orchestrator using the Windows Control Panel, some Orchestrator registry entries are not removed.

    Workaround: To remove the Orchestrator entries manually:

    1. Click Start > Run.
    2. Type regedit and press Enter.
    3. In the Registry Editor, click File > Export to back up the current registry settings.
    4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VMware.
    5. Right-click the Orchestrator entries and select Delete.
  • After upgrading Orchestrator as part of vCenter Server to 5.5, you might not be able to start the Orchestrator server.
    If the Orchestrator Administrators group and the Administrators group of the vCenter Server local machine are identical, and the local machine name has been changed after the latest vCenter Server installation, the Orchestrator server might not start successfully after the upgrade to Orchestrator 5.5. Workaround: Before starting the Orchestrator server after the upgrade to 5.5, configure the authentication settings and upgrade the database from the Orchestrator configuration interface.
  • After upgrading to Orchestrator 5.5, scheduled tasks might not run.
    After upgrading to Orchestrator 5.5 and starting the Orchestrator server, scheduled tasks might not run because Orchestrator cannot retrieve tokens from Single Sign-On for the users who scheduled the tasks.

    Workaround: Edit the tasks and re-enter the user credentials.

  • After upgrading to Orchestrator 5.5 and if Single Sign-On authentication is used, running workflows might not complete successfully.
    After upgrading to Orchestrator 5.5 and starting the Orchestrator server, workflows that were in running state or waiting on user interactions before the upgrade might not complete successfully if Single Sign-On authentication is used.

    Workaround: Restart the workflows.

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

  • Orchestrator Appliance DNS configuration resets after restart
    If you set the networking configuration when deploying the Orchestrator Appliance OVF, you cannot change the DNS for the Orchestrator Appliance by using the administrator interface (https://orchestrator_appliance_ip:5480). If you change the DNS value, the new DNS value is accepted, but after restarting the Orchestrator Appliance, the DNS value reverts to the value set during the OVF deployment.

    Workaround 1: If you have not deployed the OVF yet, set the network configuration after the completing the deployment.

    Workaround 2: If you have set the networking configuration during the OVF deployment, edit the OVF settings of the Orchestrator Appliance and change the DNS value. You should repeat this for every change of DNS.

  • Unable to start the Orchestrator server when Oracle Database 12c is used
    The Orchestrator server cannot start when it is configured to use Oracle Database 12c.

    Workaround: To be able to use Oracle Database 12c:

    1. Navigate to the Orchestrator server installation folder and open the vmo.properties file for editing.
      • If you have installed Orchestrator on a Microsoft Windows machine, navigate to:
        orchestrator_installation_folder\app-server\conf\vmo.properties
      • If you use the Orchestrator Appliance, in the Linux console, navigate to:
        /etc/vco/app-server/vmo.properties
    2. Set the value of the database.hibernate.dialect property to:
      database.hibernate.dialect=org.hibernate.dialect.Oracle10gDialect
    3. If you use the Orchestrator Appliance, verify that the owner of the file is vco.
      To set vco as the owner of the file, run the following command:
      chown vco:vco /etc/vco/app-server/vmo.properties
    4. Restart the Orchestrator server:
      1. In the Orchestrator configuration interface, click the Startup Options tab.
      2. Click Restart service.
  • After you modify the Single Sign-On settings by running a workflow from the Configuration plug-in, you must immediately restart the Orchestrator server
    You must always restart the Orchestrator server right after running a workflow for configuring the Single Sign-On settings, otherwise the Orchestrator server might become unavailable. The new Single Sign-On settings will be applied after the server restart. For this reason, if you are performing an automatic configuration of Orchestrator server through workflows, make sure that the Single Sign-On configuration is the last step of the process and is performed right before the Orchestrator server restart.

  • The Orchestrator authentication configuration might become invalid
    When Orchestrator is configured to use vCenter Single Sign-On, if the certificate of the vCenter Single Sign-On server changes or regenerates, the Orchestrator authentication configuration becomes invalid and the Orchestrator server cannot start.

    Workaround: To fix this issue, import the new vCenter Single Sign-On certificate:

    1. Log in to the Orchestrator configuration interface as vmware.
    2. Click Network.
    3. In the right pane, click the SSL Trust Manager tab.
    4. Load the vCenter Single Sign-On SSL certificate from a URL or a file.
    5. Click Import.
    6. Click Startup Options.
    7. Click Restart the Orchestrator configuration server to restart the Orchestrator Configuration service after adding the new SSL certificate.

  • 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.

  • Support for TNSNames missing when you connect to an Oracle database
    You cannot use TNSNames to connect to an Oracle database. You can connect to an Oracle database using an IP address or a DNS name.

    Workaround: Add support for RAC and TNS configuration for Oracle 11g Database instances to vCenter Orchestrator (KB 1022828).

  • SSL certificate is lost when you import configuration from previous installation
    If you import the configuration of a previous installation into the current installation, the SSL certificate from the old installation is not loaded. In the Orchestrator configuration interface the Server Certificate tab shows a red triangle.

    Workaround: You must import the certificate manually.

  • Restricted access to vCenter Server inventory can cause errors if you set Session per user
    If you select the Session per user option in the vCenter Server tab of the configuration interface, accessing the vCenter Server inventory can result in some errors if the connected user has restricted access to inventory objects.

  • No error message is displayed on the Network tab of the Orchestrator configuration interface when a network port is already in use
    The Network configuration is saved successfully without errors even when the port numbers that you enter are already taken on your host.

    Workaround: Make sure the port numbers you enter on the Network tab are free.

Networking Issues

  • Loss of network connection to vCenter Server can cause workflows to stop
    If Orchestrator loses the network connection to vCenter Server while a workflow is running, and if the workflow attempts to access vCenter Server, that workflow stops and does not attempt to restart. Furthermore, the vCenter Server plug-in flushes its cache if it loses the connection to vCenter Server. Consequently, when the Orchestrator server restarts, it fetches all running objects again from the vCenter Server rather than reloading them from the cache. Fetching the objects again can cause peaks in CPU usage, and increases the load on vCenter Server. An intermittent connection to vCenter Server causes frequent workflow failures. If the network connection to vCenter Server is intermittent, then constantly fetching the objects can consume vCenter Server memory, leading to drops in performance.

    Workaround: Ensure that the network connection to vCenter Server is stable.

Client Issues

  • Incorrect number of elements might appear in the workflow editor presentation
    When you are editing a workflow which has an array of inputs or attributes and you view details about its elements from the Attributes pane on the General tab, an incorrect total number of items might be displayed. If the array has more than six elements, the number of displayed elements is one less than the actual number of elements.
  • Using special characters in the workflow presentation might cause issues
    If you use special characters when you define the workflow presentation, the output text might not appear correctly. For example, if you use the & character followed by a string of characters that do not conform to HTML format standards, the & character and all following characters do not appear in the workflow presentation.

  • Usage of the Orchestrator client through Java WebStart if the Orchestrator Appliance is behind Network Address Translation (NAT) is not supported
  • The Revert option for the parameters table on the Scripting tab of the Edit Actions view does not revert to the last saved state
    When you add a parameter to an action script, you cannot remove it using the Revert option.

    Workaround: Right-click the parameter and click Delete Selected.

  • Characters are accepted as the input value for workflow attributes of number type
    Format validation has been disabled on workflow attributes that are of the number type. Invalid input values are accepted without any warning, and workflows are saved successfully, which can lead to unpredictable results.

  • Changes to input parameter descriptions are not propagated to the presentation
    If you change the description of an input parameter for a workflow, the change is not propagated to the description in the presentation.

    Workaround: Copy the description to the presentation manually.

Miscellaneous Issues

  • Issues with REST API enumerated types
    If you send a GET request to https://orchestrator_host:8281/vco/api/catalog/Enums/enum_type/, you receive an error message of the type HTTP Status 404 - ch.dunes.model.sdk.SDKFinderException: Unable to execute 'fetchAll' for type : enum_type. This prevents searching for enumerated types by using the Orchestrator REST API. However, running and validation of the presentation instance or workflow run is not affected if you provide a valid SDK object type, for example:
    <parameter type="Enums:MSTimeZone" name="inEnum" scope="local">
    <sdk-object type="Enums:MSTimeZone" href="https://orchestrator_host:8281/vco/api/catalog/Enums/MSTimeZone/125/" id="125"/>
    </parameter>
  • A generated URL might lead to an error of the type: Page not found
    When you run a workflow that sends an email with a URL requiring a user interaction, after you click the URL, it opens the weboperator Web view page with an error of the type: Page not found. This issue occurs when Orchestrator is configured to use 0.0.0.0 as an IP address.
  • Workaround: Configure Orchestrator to use another IP address:

  1. Log in to the Orchestrator configuration interface as vmware.
  2. On the Network tab configure the Orchestrator IP address.
  3. Click Apply changes.

  • Orchestrator does not support slashes in workflow names
    If you have a workflow with a slash in its name, when you run the workflow, the workflow token might never change to completed, although the workflow itself has completed running.

    Workaround: Remove the slash from the name of the workflow.

  • 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.
  • You cannot collect Orchestrator log bundle together with the vCenter Server log bundle
    When Orchestrator and vCenter Server are installed on the same machine, and you collect the vCenter Server log bundle, the Orchestrator log files are not included in the bundle ZIP file. You can collect the Orchestrator log files only from the Orchestrator configuration interface. To gather log files from Orchestrator:
    1. Go to the Orchestrator configuration interface at https://orchestrator_server_ip_address:8283.
    2. Log in with your username and password.
    3. Click Logs.
    4. Click Generate log report.
    5. Save the generated ZIP file.

  • 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.
  • [an error occurred while processing this directive]