VMware

VMware vCenter Orchestrator 4.0 Release Notes

vCenter Orchestrator 4.0 | 15 April 2009 | Build 4240

vCenter Server 4.0 | 24 April 2009 | Build 162856

Last Document Update:14 Mar 2011

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

If you have downloaded and installed VMware vCenter Server, Orchestrator is already installed on your system and only needs configuration.

Read the VMware vCenter Orchestrator Installation and Configuration Guide for step-by-step guidance on configuring vCenter Orchestrator.

Upgrading or Migrating to vCenter Orchestrator 4.0

Upgrades from the vCenter Server 4.0 Release Candidate and Orchestrator Beta releases to vCenter Server 4.0 and Orchestrator 4.0 are not supported. Uninstall vCenter Server 4.0 Release Candidate and Orchestrator 4.0 Beta, and perform fresh installations of vCenter Server 4.0 and Orchestrator 4.0.

If you have developed workflows, actions, plug-ins, policies, and so on 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.0.
  3. Install and Configure Orchestrator 4.0 by following the instructions of the VMware vCenter Orchestrator Installation and Configuration Guide.
  4. Connect Orchestrator 4.0 to the new Orchestrator database.
  5. Import the packages you exported from the older version of Orchestrator.

Read the "Refactoring Orchestrator Applications After Upgrading vCenter" section of the VMware vCenter Orchestrator Developer's Guide for instruction on how to upgrade existing Orchestrator packages to this version.

Compatibility

Orchestrator's vCenter 4.0 plug-in is fully supported for use with vCenter 4.0. However, using the vCenter Server 4.0 plug-in with vCenter Server 2.5 is not supported. To use Orchestrator 4.0 with vCenter Server 2.5, you must install Orchestrator's Virtual Infrastructure 3 plug-in.

Enable Support for Oracle Databases

To use an Oracle database, you must download the driver and copy it to the appropriate locations. The Orchestrator installer does not install drivers for Oracle databases.

  1. Download the latest Oracle JDBC driver from the Oracle JDBC drivers Web page.
    The download you need is Oracle Database 10g Release 2 (10.2.0.4), (10.2.0.3), (10.2.0.2), (10.2.0.1.0) drivers.
  2. Extract the downloaded archive.
  3. In the extracted folder, locate the file named ojdbc14.jar.
  4. To make the driver available to VMware vCenter Orchestrator server and VMware vCenter Orchestrator configuration interface, copy ojdbc14.jar to the following locations:
    • VMware vCenter Orchestrator configuration interface:
      C:\Program Files\VMware\Orchestrator\configuration\jetty\lib\ext\
    • VMware vCenter Orchestrator server:
      C:\Program Files\VMware\Orchestrator\app-server\server\vmo\lib\
  5. Restart the Orchestrator server.
    1. Right-click My Computer on your desktop and select Manage.
    2. In the Computer Management dialog box, expand Services and Applications and select Services.
    3. In the right pane, right-click and select VMware vCenter Orchestrator Server > Restart.
    4. In the right pane, right-click and select VMware vCenter Orchestrator Configuration > Restart.

The Oracle JDBC driver is installed.

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.

VMware Support's commitment to SRs filed by customers and instructions on how to file an SR can be found at http://www.vmware.com/support/services/.

For experienced SR users, file your support requests at http://www.vmware.com/support/sr/sr_login.jsp.

Use your registered VMware store account to log in.

Please 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, please 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. Enter 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 login.

Known Issues

The following known issues have been discovered through rigorous testing and will help you understand some problems you might encounter in this release. The list of issues below pertains to this release of VMware vCenter Orchestrator only. Please test future releases of vCenter Orchestrator for possible improvements and fixes.

List of Known Issues

The known issues are grouped as follows:

Installation Issues
  • The installer_debug.txt file is not removed when Orchestrator is uninstalled.

    Orchestrator installer creates a file called installer_debug.txt that is not deleted when you uninstall Orchestrator from command line or Windows Control Panel.

    Workaround: Delete the Install_Directory\installer_debug.txt file manually.

  • Orchestrator registry remains after you uninstall Orchestrator by using Windows Control Panel.

    If you installed Orchestrator by installing vCenter Server 4, and you uninstall Orchestrator using the Windows Control Panel, some Orchestrator registry entries are not removed.

    Workaround: Remove the entries manually, as follows.

    1. Click Start > Run
    2. Type regedit
    3. Navigate to HKEY_LOCAL_MACHINE | SOFTWARE | Wow6432Node | VMware Infrastructure | Orchestrator
    4. Right-click the Orchestrator entries and select Delete
Networking Issues
  • Loss of network connection to vCenter Server 4 can cause workflows to abort.

    If Orchestrator loses the network connection to vCenter Server 4 while a workflow is running, and if the workflow attempts to access vCenter Server, that workflow will abort and will not attempt to restart. An intermittent connection to vCenter Server causes frequent workflow failure. Furthermore, the vCenter Server 4 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. 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.

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

  • Server restarts when performing swapping or when running with a heavy load.

    If the Orchestrator server is running with a heavy load, for example if you have connected Orchestrator to many vCenter Servers which are running many virtual machines, or if the server is performing swapping, you might experience an unwanted server restart. The server restart is due to the default timeout that the Orchestrator watchdog service sets. In certain circumstances, if a response time exceeds the watchdog timeout period, the watchdog can falsely detect a JVM error, which leads to a server restart.

    Workaround: If you experience this behavior, you can extend the watchdog timeout period by adding or modifying the timeout parameter in the Orchestrator wrapper configuration file, wrapper.conf. The wrapper.conf file defines the wrapping of the Orchestrator server in the host system. See the section "Set the Service Timeout Parameter" in the VMware vCenter Orchestrator Installation and Configuration Guide.

  • Microsoft plug-in configuration requires the LDAP host to be set to the Domain Controller name.

    Calling the ActiveDirectory.getDC() method returns null if the IP address or DNS name is used in the LDAP configuration settings of the Microsoft plug-in.

    Workaround: Configure the Microsoft plug-in as follows:

    1. Log in to the Orchestrator configuration interface as vmware.
    2. Click the Microsoft tab in the left pane.
    3. Enter the Domain Controller name in the LDAP host text box.
    4. Click Apply changes.
  • Debug screen appears if Orchestrator client runs out of memory.

    If the Orchestrator client runs out of memory, for example if you are loading a workflow element that contains a very large array of objects, the debug screen appears and the client freezes.

    Workaround: Close the client and allocate more memory to the Orchestrator client, as follows:

    1. Navigate to the following directory:
      1. install_directory\VMware\Orchestrator\apps if you installed the standalone version of Orchestrator
      2. install_directory\VMware\Infrastructure\Orchestrator\apps if the vCenter Server installer installed Orchestrator
    2. Open the file vCenter Orchestrator Client.lax in a text editor.
    3. Locate the entry lax.nl.java.option.java.heap.size.max.
    4. Increase the value of lax.nl.java.option.java.heap.size.max, for example to 512Mb.
    5. Save vCenter Orchestrator Client.lax.
    6. Restart the Orchestrator client.
Miscellaneous Issues
  • New: Security vulnerabilities in the Apache Struts version embedded in Orchestrator

    The following VMware vCenter Orchestrator (vCO) versions embed Apache Struts 2.0.11 or earlier:

    • vCenter Orchestrator 4.0
    • vCenter Orchestrator 4.0 Update 1
    • vCenter Orchestrator 4.0 Update 2
    • vCenter Orchestrator 4.1
    • vCenter Orchestrator 4.1 Update 1

    A remote security vulnerability that might allow unauthorized users to run code on the vCO system without authentication is reported for Apache Struts version 2.0.11 and earlier (http://struts.apache.org/2.2.1/docs/s2-005.html). The Common Vulnerabilities and Exposures project has assigned the name CVE-2010-1870 to this vulnerability.

    Apache Struts version 2.0.11 and earlier also contain vulnerabilities described at the following URLs:

    The vulnerabilities are classified as Important, according to the VMware Security Response Policy.

    Workaround: To resolve this issue, perform the steps described in Workarounds for vCenter Orchestrator Address Apache Struts Remote Code Execution Vulnerability (KB 1034175).
  • Orchestrator 4.0 is only supported in the en_US locale.

  • Possible loss of logs when using vmo.bat file to restart Orchestrator server.

    If you start the Orchestrator server as a service and you then restart the Orchestrator server by running the vmo.bat file directly, you can experience a potential loss of logs. The loss of logs is due to the Orchestrator server potentially running with different permissions if you started it as a service and then restarted it using the vmo.bat file.

    Workaround: Do not restart the server by using the vmo.bat file. Start the Orchestrator server as a service as follows:

    1. Right-click My Computer and select Manage > Services and Applications > Services
    2. Right-click VMware vCenter Orchestrator Server and select Start.

  • The number of virtual CPUs you can add when you run the Create VM workflows is limited to 4.

    When you create a virtual machine using the vSphere client, you can add up to 8 CPUs. With the Create VM workflows you can add up to 4 virtual CPUs. This is a limitation of vCenter Orchestrator 4.0.

  • Plug-in method behavior depends on exact Java signature.

    For example, if you map a JavaScript method foo() to a Java method bar(), which takes an integer as a parameter and returns it, you can implement the Java code for foo() in two different ways:

    1. int bar(int i) { return i; }
      In this case, the call to foo() is the same as foo(null), which translates to bar(0), which returns 0 in Java, and then returns 0 in JavaScript, because null implicitly converts to 0 in an integral context
    2. Integer bar(Integer i) { return i; }
      In this case, the call to foo() is the same as foo(null), which translates to bar(null), which returns null in Java, and then returns null in JavaScript. Because this code uses objects instead of integral contexts, no conversion takes place.

    Workaround: Plug-in developers must be aware of this implementation detail, since it can change the results of a function when omitting some arguments or using null explicitly.

  • No input parameters are displayed in the drop-down menu for the Decision workflow schema element.

    You cannot define or edit the decision statement because the possible input parameters are not visible on the Decision schema element's properties tab.

    Workaround: Use a Custom Decision schema element.

  • The Remove host workflow fails to remove a standalone ESX host from vCenter.

    You can run the Remove host workflow on an ESX host which is inside a cluster and in maintenance mode.