VMware

VMware vCenter Orchestrator 4.2.1 Release Notes

vCenter Orchestrator 4.2.1 | 15 Mar 2012 | Build 555

vCenter Orchestrator Appliance 4.2.1 | 15 Mar 2012 | Build 612841

Last Document Update: 10 Apr 2012

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Downloading and Installing VMware vCenter Orchestrator 4.2.1

You can install Orchestrator 4.2.1 only on 64-bit operating system platform. If you have downloaded and installed VMware vCenter Server 5.0 Update 1, Orchestrator is already installed on your system and only needs configuration.

Read Installing and Configuring VMware vCenter Orchestrator for step-by-step guidance on configuring vCenter Orchestrator.

Upgrading to vCenter Orchestrator 4.2.1 and Migrating the Orchestrator Configuration Data

To upgrade an installation of Orchestrator 4.1 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 4.2.1 by upgrading to vCenter Server 5.0 Update 1. To upgrade to vCenter Orchestrator 4.2.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:

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

Downloading and Deploying the VMware vCenter Orchestrator Appliance 4.2.1

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.

The vCenter Orchestrator appliance is distributed as an OVF (Open Virtual Machine Format). It is pre-built and pre-configured with Novell SUSE Linux Enterprise Server, PostgreSQL, and OpenLDAP, and it can be used with vCenter Server 4.1 and later. You can download the Orchestrator appliance from the VMware Web site.

The vCenter 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 to use external ones like Active Directory or Oracle.

The vCenter 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.

For instructions about deploying and using the Orchestrator appliance, see Using the vCenter Orchestrator Appliance.

Internationalization (I18N) Support

vCenter Orchestrator 4.2.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 through:

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

  1. Go to the Orchestrator configuration interface at http://orchestrator_server_ip_address:8282.
  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 http://orchestrator_server_ip_address:8282.
  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 forum at http://communities.vmware.com/community/vmtn/mgmt/orchestrator. Use your registered VMware store account to log in.

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:

vCenter Orchestrator 4.2.1 Feature and Support Notice

vCenter Orchestrator 4.2.1 and its subsequent releases no longer support the default remote login to the Orchestrator configuration interface. For instructions on how to enable the Orchestrator configuration interface for remote connection, see Installing and Configuring VMware vCenter Orchestrator.

Resolved Issues

The following list of issues is resolved in this release:

  • vCenter Orchestrator password disclosure
    The vCenter Orchestrator Web Configuration tool reflects back the vCenter Server password as part of the Web page. This might allow the logged-in Orchestrator administrator to retrieve the vCenter Server password. The Common Vulnerabilities and Exposures project (www.cve.mitre.org) has assigned the name CVE-2012-1513 to this issue.

    This issue is resolved in this release.

  • Workflow validation fails although the code is correct
    The usual code for calling an Orchestrator action is System.getModule("someModule").someAction();. If you split this into declaration, followed by an action call, for example:
    var module = System.getModule("someModule");
    module.someAction();

    the workflow validation fails.

    This issue is resolved in this release.

  • You cannot import a certificate in Orchestrator if the certificate is not a CSR file
    When you try to import a certificate in Orchestrator, and the certificate is not in CSR file format, for example, it is a CER file, the Orchestrator configuration interface does not accept the file and reports an error.

    This issue is resolved in this release.

  • You cannot re-insert a timeout.date or security.group attribute value
    When you work with user interactions, you cannot re-insert a timeout.date attribute that has already been removed. The reason is that you are not allowed to type a period in the attribute name field. As a result, you cannot use an existing user interaction with a timeout value.
    This issue occurs because SOAP clients can only refer to the internal name (itemNN) instead of the description, and with each newly created item, a different name is generated for the item. This way, every existing workflow has to be changed when the modification is requested. The same is valid for the security.group attribute.

    This issue is resolved in this release.

  • SOAP clients cannot determine external input for user interactions
    SOAP clients cannot determine the required or permitted external input parameters (name or type) for user interactions in workflows in contrast to input and output parameters for workflows.

    This issue is resolved in this release.

  • The Orchestrator client cannot create Configurations attributes that contain a hyphen
    By using the Orchestrator client you cannot create Configurations attributes that contain a hyphen. However, you can create attributes with such names by using the setAttributeWithKey() API call.

    This issue is resolved in this release.

  • A workflow might stop responding for a long time
    A current workflow run might stop responding indefinitely if the LockingSystem.lockAndWait() API method is called with parameters exceeding 100 characters in length.

    This issue is resolved in this release.

  • A workflow run does not provide enough information in the scripting log output
    There is no direct correlation between the current workflow run and the output written in the scripting log (app-server/server/vmo/log/script-logs.log). Workflows can use the System.log() method to add debug or other information to the Orchestrator scripting log. The information in the log can help in troubleshooting and debugging customer-developed workflows. However, the log entry does not provide enough information to determine which workflow execution has added the particular output.

    The issue is resolved in this release, and for clarity purposes, an additional prefix is added to each line in the scripting log to describe the workflow run. The line format is changed to:
    <Date> <Severity> [SCRIPTING_LOG] [<Workflow> (<Execution start date>)] <Message>

  • Workflow string attribute is null when the workflow is linked to from other workflow
    If a workflow defines a string attribute, the attribute value is an empty string when the workflow is run directly. When the workflow is linked from another workflow, the string attribute is null.

    This issue is resolved in this release and string attributes are an empty string (their value is "") initially. String attributes have a null value if they are explicitly nullified in a scriptable task element.

  • Object literals are not properly transferred as Properties objects
    Properties is an object that contains one or more key-value pairs. JavaScript contains special construction to define such objects as an object literal. However, the workflow engine does not recognize these object literals as objects of type Properties, although they have very similar semantics. Consequently, such objects are null when assigned to a workflow variable.

    This issue is resolved in this release.

  • The Add hours to date function produces an error
    When the Add hours to date element from the Basic palette is added to the workflow and the input and output parameters are correctly wired, the workflow run fails with the error: [I] TypeError: Cannot find function addHours. (Workflow:date / Add hours to date (item0)#2)

    This issue is resolved in this release, and the Add hours to date element is replaced with the addHoursToDate action in the com.vmware.library.date module. The action can be used the same way as the Add hours to date element.

  • The virtual machine is cloned successfully but the workflow fails
    When you clone a virtual machine by using the Clone, Windows Sysprep with single NIC and credential workflow, the process successfully creates a new virtual machine but fails to start a customization. The cause is an incorrect default license key that is used in the customization process. The issue is visible in the sysprep log files on the newly created virtual machine or while tracking the workflow run.

    This issue is resolved in this release.

  • Incorrect file path appearing in multiple browsers while using the Orchestrator configuration interface
    When you import a configuration file or install an application from the Orchestrator configuration interface and you select a local file (for example, file.txt), the path that appears in the input field is C:\fakepath\file.txt in Google Chrome or a similar address in other browsers containing the fakepath string.
    The issue depends on the browser you use and how it implements the W3C recommendation about uploading files from HTML elements.

    This issue is resolved in this release.

  • SSH 1.0.3 Plug-in is unable to transfer files larger than 2KB in size
    Sometimes files copied using the SSHSession.getFile() scripting API get corrupt. Using SSH to fetch files that are sized from 1KB to 2KB from arbitrary UNIX/Linux servers or storage locations to the Orchestrator server works correctly. Larger files might be corrupted, accumulated sporadically, and often have the last file lines cut off.

    This issue is resolved in this release.

  • The weboperator Web view might not display the schema image of a workflow
    When you select a workflow in the weboperator Web view and click the Schema tab, the schema might not load.

    This issue is resolved in this release.

  • vm property or method not found on VcClusterAntiAffinityRuleSpec object
    You can assign a value to the vm property of a VcClusterAffinityRuleSpec or a VcClusterAntyAffinityRuleSpec object in a scriptable task of the workflow that you design. When you run the workflow, it fails with the following error message: Property or method 'vm' not found on object VcClusterAntiAffinityRuleSpec.

    This issue is resolved in this release.

  • In the API explorer, the executions property of a workflow object is incorrectly shown to be of type Object
    When you browse through the API explorer, the executions property is categorized as Object. The actual type of the execution property is an array of WorkflowTokens.

    This issue is resolved in this release.

  • Incorrect error message displayed when you use Reference Error construct
    Some workflows in the Orchestrator library use the new ReferenceError() function in their scripting to mark errors. However, Rhino scripting does not unwrap the error message correctly, and the root cause of the error remains unclear. You should not use the new ReferenceError('<<message>>') construct in your scripting. If you have such a construct, replace it with a simple throw <<message>>. You can clone system workflows to apply the fix.

    This issue is resolved in this release.

  • Virtual machine power state values are not listed while creating an IF condition based on the virtual machine power state
    When you create an IF condition based on the virtual machine power state, you cannot select a value from the pop-up window as no values are listed.

    This issue is resolved in this release.

  • Orchestrator cannot connect to remote SQL servers by using dynamic ports

    This issue is resolved in this release.

  • The library used in the SSH plug-in is updated
    The library used in the SSH plug-in is updated to provide the following new capabilities:
    • Added attribute Boolean property to SSHSession object
    • Added attribute string terminal to SSHSession object
    • Added method addEnvironment(string key, string value) to SSHSession object

    The Jcraft JSch version is also updated from version 0.1.29 to version 0.1.42.

  • Relocate virtual machine disks workflow might fail with a non-descriptive error message
    When you try to relocate a virtual machine by using the Relocate virtual machine disks workflow, it cannot move both the disks and the virtual machine at the same time, in case the virtual machine is powered on. The workflow might fail with a non-descriptive error message.

    The issue is resolved in this release and Orchestrator checks whether the virtual machine is powered on. If the virtual machine is powered on, the workflow fails with an error message stating that to migrate both the disks and the virtual machine at the same time, the virtual machine must be powered off.

  • Active sessions are not cleaned up after Orchestrator client is closed
    Active sessions are not cleaned up after the Orchestrator client is closed. Consequently, with every new Orchestrator client login, more and more resources are consumed on the server.

    This issue is resolved in this release.

  • Some obsolete parameters are removed from the Set virtual machine performance workflow
    Obsolete parameters related to the virtual machine network settings are removed from the Set virtual machine performance workflow, because these parameters are not supported by ESX/ESXi hosts. The removed parameters are:
    • setNetwork
    • netAverageBps
    • netBurstSize
    • netPeakBps
    • netShapeEnabled

    To set the network shaping parameters for a virtual switch on an ESX/ESXi host, you can use Update standard virtual switch or Update port group in standard virtual switch workflows.

  • vCenter Server task trigger cannot be activated
    If you run a workflow that contains a vCenter Server trigger and you use the Inventory Service, the trigger cannot be activated and the workflow remains in suspended mode.

    This issue is resolved in this release.

  • Setting a failover host to an FDM/HA configuration might fail with an error message
    When you set a failover host to an FDM/HA configuration by using the VcClusterFailoverHostAdmissionControlPolicy object, you might receive the following error message: A specified parameter is not correct.

    This issue is resolved in this release.

  • Input parameters cannot be selected from some of the drop-down menus for the Decision workflow schema element
    You cannot define or edit the decision statement using the state equals or connectionState equal items. The possible input parameters are not visible on the Decision tab of the Decision schema element.

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows:

Installation Issues

  • After you upgrade the Orchestrator appliance to version 4.2.1, the Orchestrator server might not start automatically
    After you upgrade the Orchestrator appliance from version 4.2 to version 4.2.1, the Orchestrator server does not start automatically.

    Workaround: Start the Orchestrator Configuration interface and manually update the database table. After that you should be able to start the Orchestrator server. To update the database table:

    1. Log in to the appliance home page.
    2. Click Orchestrator Configuration, and log in.
    3. Click the Database tab on the left, and click Update database.
    4. Click the Startup Options tab on the left.
    5. Click Start service.

  • You might not be able to back up the Orchestrator configuration by using the data migration tool
    The backup of the Orchestrator configuration results in an error when you run the backup.bat file without changing the location to the folder where you extracted the data migration tool.

    Workaround: In the Windows command prompt navigate to the folder in which you extracted the data migration tool, type backup.bat, and press Enter.

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

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 does not work with forest and external trusts in Active Directory

    Multiple domains that have a two-way trust, but are not in the same tree, 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 4.1.1 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.

Miscellaneous Issues

  • New: You might not be able to import workflows and actions
    When you try to import workflows or actions as a user without administrative privileges, even if your user role has import permissions, you might not be able to import the objects.
    Workaround: Follow the instructions from: Issues with vCenter Orchestrator permissions (KB 2016770).
  • You might not be able to schedule a workflow from the weboperator Web view
    When you try to schedule a workflow from the weboperator Web view, you receive an error message: Error: XMLHttpTransport Error: 500 Internal Server Error(type: error) 'err'.
    Workaround: Follow the instructions from: Issues with vCenter Orchestrator weboperator Web view (KB 2015178).
  • Default values for input parameters are incorrectly handled in the weboperator Web view
    When you use default values for input parameters in a workflow, run the workflow from the weboperator Web view, and then you change some of the parameters, the default values are updated only when the presentations starts, not when the value of the parameter is changed.
    Workaround: Follow the instructions from: Issues with vCenter Orchestrator weboperator Web view (KB 2015178).
  • The Weboperator Web View might display the HTML tags in the Web browser
    When com.vmware.o11n.webview.htmlescaping.disabled is set to false, or is not set at all, the HTML tags from the Orchestrator presentation layer are displayed literally in the Web view.
  • You might not be able to start the Orchestrator client from the Orchestrator appliance home page on Windows XP
    You might not be able to start the Orchestrator client from the appliance home page by using Java Web Start on Windows XP. The error message that you receive states that an unsigned .jar file has been found in the application. This is an issue of the Java Web Start software.

    Workaround: Enable caching of temporary files in the Java Web Start configuration. To do this:

    1. On the Windows XP machine, click Start > Settings > Control Panel > Java.
      The Java Control Panel window opens.
    2. On the General tab, under Temporary Internet files, click Settings.
    3. Select Keep temporary files on my computer.
    4. Set the amount of disk space for storing temporary files to maximum, and click OK.
    5. Under Temporary Internet files, click View.
    6. In the Java Cache Viewer, select Applications.
    7. Select all items and remove them by clicking the Remove selected items button in the toolbar.
    8. Click Close.
    9. Click OK to close the Java Control Panel window.
    10. Click Start Orchestrator Client on the appliance home page to try to start the Orchestrator client by using the Java Web Start.
  • A generated URL requiring user interaction might lead to an error of the type: Error: 500
    When you use the Orchestrator appliance and 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: Error: 500.

    Workaround: To make the URL open the weboperator Web view correctly, add the com.vmware.o11n.webview.htmlescaping.disabled=true property to the vmo.properties file. By default, the vmo.properties file is located in /opt/vmo/app-server/server/vmo/conf.

  • Usage of the Orchestrator client through Java Web Start if the Orchestrator appliance is behind Network Address Translation (NAT) is not supported
  • Usage of the Orchestrator client through Java Web Start from the Orchestrator appliance home page if you have the Java Runtime Environment (JRE) 7 on your machine is not supported
    If the Java Runtime Environment (JRE) on your machine is of version 7, when you click the Start Orchestrator Client on the Orchestrator appliance home page, the Orchestrator client starts, but when you type in your credentials and the Orchestrator client attempts to connect to the server, the window disappears with no error.
  • The Orchestrator client might stop displaying the vCenter Server inventory
    A running environment of Orchestrator and vCenter Server plug-in might stop working properly. For example, you might not be able to browse the inventory, or when you run a workflow, instead of being able to search the vCenter Server inventory by filtered objects, the whole vCenter Server inventory is displayed. This issue occurs when Orchestrator is configured to work with the vCenter Server Virtual Appliance. When the Orchestrator session with vCenter Server becomes invalid, you cannot browse the inventory.

    Workaround: Restart the Orchestrator server.

  • 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 http://orchestrator_server_ip_address:8282.
    2. Log in with your username and password.
    3. Click Logs.
    4. Click Generate log report.
    5. Save the generated ZIP file.
  • Importing a package using the Orchestrator client fails occasionally
    Occasionally, importing a package using the Orchestrator client results in the error Unable to import a certificate, reason : Unable to save keystore.

    Workaround: Close the error message and attempt the import again.

  • The Used plug-ins tab in the Orchestrator client does not appear at all or does not list the plug-ins associated with the selected package
    You cannot check dependencies between packages because the Used plug-ins tab is either not displayed or not populated with the list of associated plug-ins. If the tab is not displayed and the Orchestrator client is not refreshed, you must click another tab or view.
  • The Orchestrator client stops responding if you use the Used plug-ins tab in edit mode
    When you attempt to insert or remove associated plug-ins on the Used plug-ins tab, the Orchestrator client stops responding.

    Workaround: Restart the Orchestrator client.

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

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