VMware

vCloud Director 5.5.1.2 Release Notes

vCloud Director 5.5.1.2 | 12 JUN 2014 | Build 1881717

Last updated: 29 OCT 2014

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of vCloud Director 5.5.1.2 addresses the OpenSSL security vulnerability in the Client Integration Plug-In documented in the Resolved Issues section.

Customers using vCloud Director 5.5.0, 5.5.1, or 5.5.1.1 should immediately upgrade to 5.5.1.2.

System Requirements and Installation

For information about system requirements and installation instructions, see the VMware vCloud Director Installation and Upgrade Guide.

The following upgrade paths are available.

  • Upgrade from vCloud Director 5.5.1 to vCloud Director 5.5.2. If you are a service provider, see the note below before upgrading to vCloud Director 5.5.2.
  • Upgrade from vCloud Director 5.5.1 to vCloud Director 5.6.3 for Service Providers. This upgrade option is available only if you are a service provider under the vCloud Air Network (formerly VSPP) Program.

Important note for service providers: If you upgrade to vCloud Director 5.5.2, you cannot upgrade to vCloud Director 5.6.3 for Service Providers until VMware provides a future patch. If you plan to upgrade to vCloud Director 5.6.3 for Service Providers in the near future, do not upgrade to vCloud Director 5.5.2. If you are not a service provider, you do not have access to vCloud Director 5.6.3 for Service Providers. Please check these notes again for an update on this upgrade limitation.

Documentation

To access the full set of vCloud Director 5.5.1 documentation, go to the vCloud Director Documentation page.

Resolved Issues

This release resolves the following issue.

  • OpenSSL security issues CVE-2014-0224, CVE-2014-0198, CVE-2010-5298, and CVE-2014-3470 in the Client Integration Plug-in
    The OpenSSL library for the VMware Client Integration Plug-in is updated to version openssl-1.0.1h to address OpenSSL security issues CVE-2014-0224, CVE-2014-0198, CVE-2010-5298, and CVE-2014-3470.

    After upgrading to vCloud Director 5.5.1.2, all users must update the Client Integration Plug-in.

    The vCloud Director Web console displays one of the following prompts to update the Client Integration Plug-in when you upload or download an OVF or media file or access a virtual machine console.

    An update to the Client Integration Plugin is available. Click the link below to download the installer.

    An upgrade is available for the Client Integration Plug-in. Click OK to download the plugin.

    When you see one of these prompts, take the following steps to update the Client Integration Plug-in.

    1. Download the VMware Client Integration Plug-in according to the prompt's instructions.
    2. Run the application to upgrade the Client Integration Plug-in.

      This requires restarting your Web browser.

Known Issues

The following issues are known to occur in this release of vCloud Director.

The known issues are grouped as follows:

General Issues

  • Incorrectly directed to licensing page that says vCloud Director features are unavailable
    When vCloud Director detects a licensing violation, you are redirected to the licensing page, which lists a value of No for all vCloud Director features.

    Workaround: Ignore the message and continue using vCloud Director as usual. All features are available despite the message on the licensing page.

Installation and Upgrade Issues

  • Incorrect database schema upgrade error message while upgrading vCloud Director from version 5.5.1 or 5.5.1.1. to version 5.5.1.2
    When you upgrade vCloud Director from version 5.5.1 or 5.5.1.1 to version 5.5.1.2, you are incorrectly prompted to upgrade the database schema with the following error message.

    You will need to upgrade the database schema before starting the vmware-vcd service. The product upgrade tool should be run only once per vCloud Director group. The tool may be run with the following command: /opt/vmware/vcloud-director/bin/upgrade.

    Workaround: You can safely ignore this error message.

  • Attempts to upgrade vCloud Director from version 5.1.x to version 5.5.1 fail after gateway failure
    Any upgrade of a vCloud Director 5.1.x release to vCloud Director 5.5.1 has the potential to cause one or more of the system's Edge Gateways to fail the upgrade procedure and log a message similar to the following.

    Cannot upgrade vCloud Director to 5.5: Found 1 gateways backed by unsupported edge version. Please redeploy gateways or reset vApp networks backed by edge and then run upgrade again.

    Workaround: See Pre-Upgrade Check for Potential Edge Gateway Problems.

Localization Issues

  • Host agent upgrade fails if the vCloud Director system name contains non-ASCII characters
    When you upgrade a vCloud Director system with non-ASCII characters in its name from an earlier version to version 5.5.1, the host agent upgrade fails.

    Workaround: Unprepare the host to remove the host agent, then prepare the host agent again.

  • A CD/DVD device name containing non-ASCII characters causes attempts to add the CD/DVD to a virtual machine to fail
    Attempts to add a CD/DVD device with non-ASCII characters in its name to a virtual machine fails.

    Workaround: Change the CD/DVD device name to contain only ASCII characters before adding it to a virtual machine.

  • Non-ASCII characters in VPN tunnel names appear as garbage characters in remote organizations
    When you assign a name to a VPN tunnel that includes non-ASCII characters, the non-ASCII characters in the name appear as garbage characters when you view the VPN tunnel from another organization. The VPN tunnel continues to function normally.

    Workaround: Do not use non-ASCII characters in VPN tunnel names.

  • Edge gateways cannot be created or updated with a pool server or virtual server that has non-ASCII characters in its name
    When you attempt to create an edge gateway with a pool server or virtual server that has non-ASCII characters in its name, the operation fails. When you change the name of a pool server or virtual server to include non-ASCII characters, any Edge gateways associated with the pool server or virtual server cannot be updated.

    Workaround: Do not use non-ASCII characters in the names of pool servers or virtual servers that are used for Edge gateways.

  • vApp template names cannot include only non-ASCII characters
    vCloud Director displays the error message Invalid computer name: Computer name can only contain alphanumeric characters and hyphens, and must not contain only digits. if you use only non-ASCII characters in a vApp template name.

  • In locales other than English, object lists can be filtered only by columns that contain user-generated content
    When you use vCloud Director in locales other than English, the filter function on object lists only works when you filter using columns that contain user-generated content, such as Name or vApp Name.

  • Some localized messages appear in English on Red Hat Enterprise Linux and CentOS 6.x
    On Red Hat Enterprise Linux and CentOS 6.x, some vCloud Director cells do not detect the correct locale at first start up or when the operating system is rebooted, which causes some messages to appear in English.

    Workaround: Manually restart the cell by running the command /opt/vmware/vcloud-director/bin/vmware-vcd restart.

  • Repeated prompts to install the VMware Client Integration Plug-in appear when importing a file into a catalog or opening a virtual machine console from a Windows account that contains non-ASCII characters
    When you attempt to import a file into a vCloud Director catalog or open a virtual machine console from a Windows account that has non-ASCII characters in its name, vCloud Director prompts you to install the VMware Client Integration Plug-in. This happens even when the plug-in is already installed.

    Workaround: Log in to the Windows administrator account or a user account that contains only ASCII characters in its name, and upload the file or open the firtual machine.