VMware

vCloud Director 5.5 Release Notes

vCloud Director 5.5 | 14 OCT 2013 | Build 1323688

Last updated: 29 Jan 2014

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Catalog Enhancements: Improvements to catalog functionality, including the following new catalog features.
    • Limiting access to shared catalogs
    • Publishing catalogs to external vCloud Director instances
    • Automated versioning of catalog content
    • Uploading any file type to a Catalog
  • Usability improvements for VMware vSphere vApp provisioning and life-cycle management: Improvements to vApp provisioning and life-cycle management including the following.
    • Ability to customize virtual machine hardware settings when deploying vApps from templates.
    • Support for hot-add and hot-remove of hard disks and NICs.
    • vApp clone support for running and suspended vApps to include capturing memory state
  • Import and Export vApps Directly From a Virtual Datacenter: The ability to import and export vApps directly to and from a virtual datacenter together with added support for the Open Virtual Appliance (OVA) file format.
  • CentOS Support: Support for the CentOS operating system to host the vCloud Director cell.
  • Expanded Browser and Operating System Support: Support for the VCloud Director web client has been expanded to include the following.
    • Support for Mozilla Firefox and Google Chrome on Mac OS to access the vCloud Director web client, including virtual machine consoles
    • Full support for Google Chrome on Microsoft Windows and Linux

System Requirements and Installation

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

Documentation

For vCloud Director 5.5 documentation, go to the VMware vCloud Director Documentation page.

Known Issues

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

The known issues are grouped as follows:

General Issues

  • Actions menu does not display on Mac OS using a retina display
    On Mac OS using a retina display, the Actions drop-down menu does not appear in vCloud Director. This is caused by a known issue between Adobe Flex and retina displays.

  • vCloud Director appears blurry on Mozilla Firefox running on Mac OS
    When you log in to vCloud Director web client by using the Mozilla Firefox browser on a Mac OS, the vCloud Director web client appears blurry. This is caused by a known issue between Adobe Flex and retina displays.

    Workaround: See Blurry Text on MacBook Pro with Retina Display [QuickFix].

  • Client Integration Plug-in download fails on Chrome
    When you try to upload or download an OVF for the first time, vCloud Director prompts you to install the Client Integration Plug-in. If you try to download the plug-in using Google Chrome, the download doesn't start.

    Workaround: Log in to vCloud Director using Mozilla Firefox and download and install the Client Integration Plug-in. After installing the plug-in, you can upload and download OVFs in vCloud Director using Google Chrome.

Installation and Upgrade Issues

  • Precondition for upgrading to vCloud Director 5.5 in a Chargeback environment
    vCloud Director 5.5 is supported only by Chargeback Manager 2.5.1. You must upgrade Chargeback Manager to version 2.5.1 before upgrading vCloud Director to version 5.5.

  • Unable to install or upgrade to VMware vCloud Director version 5.5.0 when using SQL Server 2005 SP4
    If you are using Microsoft SQL Server 2005 SP4 as your VMware vCloud Director database and you try to install or upgrade vCloud Director to version 5.5.0, the installation/upgrade may fail. See KB 2060068 for more information.

  • SSL connection warning after installing or upgrading vCloud Director
    To minimize the likelihood of an unsuccessful SSL connection, vCloud Director 5.5 is configured by default to disallow ciphers that are known to cause SSL connection failures. When you install or upgrade vCloud Director, the installation or upgrade script examines the cell's certificates. If any of the certificates are encrypted using one of the disallowed ciphers, the script modifies the default configuration to allow use of that cipher and displays this warning: Warning: The specified keystore contains a DSA key which has been found to cause intermittent SSL connection failures; see KB 2056026 for details.

    Workaround: Use the cell management tool to replace the cell's existing certificates with certificates that do not use a DSA-based cipher, and then reconfigure the cell's list of allowed ciphers to disallow use of DSA-based ciphers. See Using the cell-management-tool to manage the list of allowed SSL ciphers.

  • Edge gateway version error during upgrade
    Any upgrade of a vCloud Director 5.1.x release to vCloud Director 5.5 has the potential to cause one or more of the system's Edge Gateways to fail the upgrade procedure and log a message of the form:

    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.

    Redeploying the Edge Gateway does not solve this problem. For more information, see KB 2058977.

  • Upgrading an edge gateway configuring is missing from the vCloud Director 5.5 Administrator's Guide
    Information on upgrading edge gateway configuration is missing from the vCloud Director Administrator's Guide

    To upgrade the configuration on an edge gateway, complete the following steps.

    1. Click the Manage & Monitor tab and click Organization VDCs in the left pane.
    2. Double-click the organization virtual datacenter name to open the organization virtual datacenter.
    3. Click the Edge Gateways tab, right-click the edge gateway name and select Upgrade Configuration.
    4. Click Yes.

    Edge gateways with Compact configuration are upgraded to Full configuration, and edge gateways with Full configuration are upgraded to Full-4 configuration.

Localization Issues

  • Non-ASCII characters in a system name might cause NAT-routed external organization network creation to fail
    When you create an external organization network with a NAT-routed connection, the system name should contain only ASCII characters. Non-ASCII characters in the system name might cause network creation to fail.

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

  • Repeated prompts to install the VMware Client Integration Plug-in when importing a file into a catalog or opening a virtual machine console from a Windows account that contains non-ASCII characters
    When you try 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: Upload the file or open the virtual machine console from the Windows administrator account or a user account that has only ASCII character in its name.

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

Networking Issues

  • Security warning during IPSec VPN tunnel creation between organizations
    When you create a VPN tunnel from a network to a network in another organization, launching the Java applet to connect to the remote organization displays the warning Block potentially unsafe components from being run? Application contains both signed and unsigned code. This warning is the result of recent changes in Java 7 and does not indicate a security risk in this situation. It is safe to proceed with VPN tunnel creation.

  • Attempting to create an isolated organization virtual datacenter network with large subnets fails
    When you try to create an isolated organization virtual datacenter network with a subnet of /12 or less using the vCloud Director web client, the operation fails due to DHCP service restrictions.

    Workaround: Create the isolated organization virtual datacenter network with a subnet of /13 or more or disable DHCP service using the vCloud API before creating an isolated organization virtual datacenter network with a subnet of /12 or less.

  • Attempts to modify or remove an external network on a gateway configured to use a VPN tunnel fail and cause all future gateway modifications to fail
    When you attempt to modify or remove an external network from a gateway configured to use a VPN tunnel, the operation fails midway, causing the gateway to be out of sync between vCloud Director and vCenter Server. All future attempts to modify the gateway fail with an internal server error.

    Workaround: Re-deploy the gateway.

  • No suitable resource error when trying to deploy a Full-4 gateway with HA enabled if ESX Server has fewer than 8 vCPUs
    When you try to deploy a Full-4 gateway with HA enabled on an ESX Server host that has fewer than 8 vCPUs, the operation fails with the error The operation failed because no suitable resource was found.

    Workaround: Ensure that the ESX Server host has at least 8 vCPUs before deploying a FULL-4 gateway with HA enabled.

Virtual Machine and vApp Issues

  • Virtual machine console fit to screen does not function correctly on Chrome
    When you open a virtual machine console in vCloud Director using Chrome on a Windows or Linux operating system, the Fit to screen option resizes the console window, but does not fit the window to your screen.

  • Error message when canceling a blocking task for uploading vApp templates after beginning a vApp template upload
    When you enable a blocking task for uploading vApp templates, then begin a vApp template upload and cancel the blocking task in the vCloud Director web client, vCloud Director displays the error message Invalid response from server: No access to entity. Despite the error message, the blocking task is successfully canceled.

  • Insert CD/DVD from Catalog option is unresponsive when selected from a virtual machine's drop-down menu on a resource pool page
    When you right-click a virtual machine on a resource pool page and select Insert CD/DVD from Catalog, nothing happens.

    Workaround: Add the CD/DVD from the organization the virtual machine is in.

    1. Click Manage & Monitor and click Organizations.
    2. Right-click the organization and select Open.
    3. Click My Cloud and click VMs.
    4. Right-click the virtual machine and select Insert CD/DVD from Catalog.

vCloud API Issues

  • The allocatedExternalAddress query is not available to organization administrators
    The allocatedExternalAddress query is listed as available to an organization administrator even though the query results are accessible only to a system administrator. This query returns no records or references unless it is run by a system administrator.

  • Organization query provides an incorrect value for number of groups in an organization
    The response to an organization query, QueryResultOrgRecordType, provides an incorrect value for the numberOfGroups attribute. The value provided is actually the number of users in the organization. You cannot use the query service to obtain the number of groups in an organization.

  • The adminAllocatedExternalAddress query provides invalid values when the Accept header specifies API version 1.5
    The response to a query of type adminAllocatedExternalAddress contains invalid values for the org attribute when the Accept header in the query specifies API version 1.5.