VMware

vCloud Director 5.1.3.1 Release Notes

vCloud Director 5.1.3.1 | 1 JUL 2014 | Build 1881640

Last updated: 1 JUL 2014

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of vCloud Director 5.1.3.1 addresses the OpenSSL security vulnerability in the VMware Remote Console documented in the Resolved Issues section.

Customers using vCloud Director 5.1.3 should immediately upgrade to 5.1.3.1.

System Requirements and Installation

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

Documentation

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

Resolved Issues

This release resolves the following issue.

  • OpenSSL security issue CVE-2014-0224 in the VMware Remote Console
    The OpenSSL library for the VMware Remote Console is updated to version openssl-0.9.8za to address OpenSSL security issue CVE-2014-0224.

    After upgrading to vCloud Director 5.1.3.1, all users must update the VMware Remote Console. To upgrade the VMware Remote console, see VMware Remote Console Plug-in is not upgraded when you upgrade vCloud Director in the Known Issues section.

Known Issues

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

The known issues are grouped as follows:

General Issues

  • High CPU usage by the vCloud Director web interface
    When you run the vCloud Director web interface continuously for periods of a day or longer, the associated Flash process can use high levels of CPU.

    Workaround: Close and re-start the vCloud Director web interface.

  • HTTP ERROR 500 sometimes occurs when connecting to vCloud Director
    When you try to connect to vCloud Director using the web user interface or API, the error HTTP ERROR 500 sometimes appears.

    Workaround: Add the following to global.properties.

    cache.tenantcache.maxElementsInMemory=<numberOfOrgs x 5>
    // The value has to be more than the number of orgs CU may have/create before their next maintenance cycle (or) upgrade (or) cell-restart.

    cache.tenantcache.timeToIdleSeconds=10800000 //125 days
    cache.tenantcache.timeToLiveSeconds=10800000 //125 days
    // The above value means that CU may hit the issue again after 125 days. CU can increase the value according to their maintenance cycle (or) next upgrade (or) cell-restart.

  • Adobe Flex customizations are not applied when you use a different version of Adobe Flex than vCloud Director uses
    When you upload an Adobe Flex customization that is created using a version of Flex other than the one used by vCloud Director, the customization is not applied correctly.

    Workaround: For customizations for vCloud Director 5.1.3, use the Adobe Flex version 4.1.0.16076 SDK and compiler.

Installation and Upgrade Issues

  • VMware Remote Console Plug-in is not upgraded when you upgrade vCloud Director
    When you upgrade vCloud Director from version 5.1.3 to version 5.1.3.1, the VMware Remote Console Plug-in is not upgraded.

    Workaround: After upgrading to vCloud Director 5.1.3.1, manually uninstall the old VMware Remote Console Plug-in and install the latest version.

    On Windows

    1. Close all Web browsers.
    2. Click the Start menu and click Control Panel.
    3. Click Add or Remove Programs or Programs and Features.
    4. Select VMware Remote Console Plug-in 5.1 and click Uninstall.
    5. Follow the prompts to complete the uninstall process.
    6. Verify that the folder C:\Program Files (x86)\Common Files\VMware\VMware Remote Console Plug-in 5.1 exists. If the folder exists, delete or rename the folder and its contents.
    7. Log in to the vCloud Director Web client and open a virtual machine console.
    8. Follow the prompts to download and install the latest version of the VMware Remote Console Plug-in.

    On Linux

    1. Close all Web browsers.
    2. Run the command vmware-installer -u vmware-vmrc-5.1 to uninstall the VMware Remote Console Plug-in.
    3. Log in to the vCloud Director Web client and open a virtual machine console.
    4. Follow the prompts to download and install the latest version of the VMware Remote Console Plug-in.
  • Incorrect database schema upgrade error message while upgrading vCloud Director from version 5.1.3 to version 5.1.3.1
    When you upgrade vCloud Director from version 5.1.3 to version 5.1.3.1, 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.

  • Child resource pools sometimes aren't reconfigured after changing the elasticity of an allocation pool virtual datacenter and upgrading to vCloud Director 5.1.3
    When you change the elasticity of an allocation pool virtual datacenter, the elasticity of child resource pools is reconfigured when you power on vApps using those child resource pools. If you upgrade vCloud Director to version 5.1.3 after changing the elasticity of an allocation pool virtual datacenter but before powering on any vApps that use the affect child resource pools, the child resource pools are not reconfigured to reflect the new elasticity setting.

    Workaround:Cycle the elasticity of the virtual datacenter and power cycle a vApp that uses the affected child resource pool.

    1. Configure the virtual datacenter to use Elastic mode.
    2. Power off at least one vApp in all Allocation Pool organization virtual datacenters.
    3. Configure the virtual datacenter to use non-Elastic mode.
    4. Power on at least one vApp in all Allocation Pool organization virtual datacenters.
    5. Power the vApps back on.

  • Removing unused external IP addresses from sub-qllocated IP pools of the gateway fails after upgrading from vCloud Director 1.5.1
    After upgrading vCloud Director from version 1.5.1, attempting to remove unused external IP addresses from sub-allocated IP pools of a Gateway fails saying that IPs are in use.

    Workaround: If you are upgrading from vCloud Director 1.5.1, remove any unused external IP addresses from all Org Routed Networks before upgrading vCloud Director.

Localization Issues

  • Non-ASCII characters in VPN tunnel names appear as garbage characters in remote organizations
    When the name that you assign to a VPN tunnel 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.

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

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

  • 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 languages other than English, object lists can be filtered only by columns that contain user-generated content
    When using vCloud Director in languages other than English, the filter function on object lists only works when filtering using columns that contain user-generated content, such as Name or vApp Name.

  • Host agent upgrade fails when the vCloud Director system name contains non-ASCII characters
    When you upgrade a vCloud Director system with non-ASCII characters in its name from version 5.1.x to version 5.1.3, the host agent fails to upgrade.

    Workaround: Perform an uninstall to remove the host agent, then prepare the host agent again.

  • Some localized messages display 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 display in English.

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

Networking Issues

  • Trying to create an edge gateway with Full-4 configuration using vCloud Networking and Security 5.1.2a or earlier fails
    When you create an edge gateway, vCloud Director allows you to select Full-4 configuration for the gateway when you are using a version of vCloud parameters Networking and Security that doesn't support Full-4 configuration, but the create gateway operation fails.

    Workaround: Full-4 edge gateways require vCloud Networking and Security 5.1.2c or later.

Virtual Machine and vApp Issues

  • Removing the only hard disk from a powered-on virtual machine generates an error
    When you remove the only hard disk from a powered-on virtual machine, vCloud Director displays an error. Despite the error message, the disk is successfully removed.

  • Some networks are missing from the Select Organization VDC Network page of the new vApp wizard are disabled for vApp Authors

    When a vApp Author creates a new vApp network and selects Organization VDC Network in the new vApp network wizard, the number of networks displayed is off by the number of network that have already been added to the vApp. This may result in next page buttons being disabled since there are no more networks to be display in the list.

vCloud API Issues

  • API Backward Compatibility
    Incorrect DHCP information is returned in the DhcpService element when a vCloud API v1.5 client retrieves an OrgNetwork object from vCloud Director 5.1.

  • Control characters in an organization virtual datacenter name cause unmarshalling errors in vCloud Director SDKs and API
    Using the vCloud Director API or SDKs with an organization virtual datacenter that has control characters in its name, causes unmarshalling errors.

    Workaround: Do not use control characters in organization virtual datacenter names.

  • Allocation pool storage profiles do not work correctly after setting the capacity to unlimited using the vCloud Director API
    The vCloud Director mistakenly allows you to set the storage profile capacity on an allocation pool virtual datacenter to unlimited. After making this change, the storage profile cannot be updated using the vCloud Director web client.

    Workaround: Use the vCloud Director API to change the storage profile capacity to a value other than unlimited.