VMware

vCloud Director 5.5.2.1 Release Notes

vCloud Director 5.5.2.1 | 30 OCT 2014 | Build 2233543

Last updated: 12 FEB 2015

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of vCloud Director addresses an issue with opening virtual machine consoles on Google Chrome. See Resolved Issues for details.

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.2 to vCloud Director 5.5.2.1. If you are a service provider, see the note below before upgrading to vCloud Director 5.5.2.1.
  • Upgrade from vCloud Director 5.5.1 to vCloud Director 5.5.2.1. If you are a service provider, see the note below before upgrading to vCloud Director 5.5.2.1.
  • 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 or 5.5.2.1, you cannot upgrade to vCloud Director 5.6.3 for Service Providers. To upgrade to vCloud Director for Service Providers after you upgrade to vCloud Director 5.5.2 or 5.5.2.1, upgrade to vCloud Director 5.6.4 or later for Service Providers. If you are not a service provider, you do not have access to vCloud Director for Service Providers.

Documentation

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

Resolved Issues

This release resolves the following issues.

General Issues

  • OpenSSL CVE-2014-3566 security vulnerability
    OpenSSL security issue CVE-2014-3566, also known as "POODLE," affects OpenSSL 3.0. vCloud Director 5.5.2.1 disables support for OpenSSL 3. For more information, see VMware Products and CVE-2014-3566 (POODLE).

  • Attempts to download media files from a public catalog fail
    When you attempt to download a media file from a public catalog, the download operation fails. This issue is resolved in vCloud Director 5.5.2.1.

  • Attempts to download vApp templates from a shared catalog fail
    When you attempt to download a vApp template from a catalog that is shared from another organization, the operation fails. This issue is resolved in vCloud Director 5.5.2.1.

  • Changes to a vApp template made using the overwrite option in a published catalog do not sync to subscribed catalogs
    When you modify a vApp template using the overwrite option in a published catalog, the changes are not reflected in subscriptions to the public catalog. This issue is resolved in vCloud Director 5.5.2.1.

  • ISO files uploaded with .flp extension when .iso is not specified
    When you upload an ISO file and do not include the .iso extension in the file name, vCloud Director uploads the file with a .flp extension. This issue is resolved in vCloud Director 5.5.2.1.

  • Deleted users are not marked as stranded after LDAP synchronization
    When vCloud Director automatically synchronizes user and group information with the LDAP server, deleted users are not marked as stranded. This issue is resolved in vCloud Director 5.5.2.1.

Networking Issues

  • SSL certificate validation for vShield Manager fails
    When the system enforces certificate validation for SSL communication between vCloud Director and vShield Manager, SSL certificate validation for vShield Manager always fails, resulting in communication failure between vCloud Director and vShield manager. This issue is resolved in vCloud Director 5.5.2.1.

  • vCloud Director displays 0 GHz CPU allocation used for pay-as-you-go organization virtual data centers
    The vCloud Director Web console incorreclty displays 0 GHz as the CPU allocation used for pay-as-you-go organization virtual data centers that have resources guaranteed set to 0. This issue is resolved in vCloud Director 5.5.2.1.

Virtual Machine and vApp Issues

  • Attempts to open a virtual machine console on Google Chrome fail
    When you attempt to open a virtual machine console on a Google Chrome browser, the operation fails. The occurs due to the deprication of NPAPI in Google Chrome. vCloud Director 5.5.2.1 uses WebMKS instead of the VMware Remote Console to open virtual machine consoles in Google Chrome, which resolves this issue.

  • Guest customization fails with a Sysprep error
    When you attempt to use guest customization on a virtual machine, the operation fails with the following error message.

    Mount directory C: does not exist

    This issue is resolved in vCloud Director 5.5.2.1.

  • Attempting to power on a virtual machine with guest customization enabled sometimes fails
    When you attempt to power on a virtual machine with guest customization enabled on a provider virtual data center where one or more ESXi hosts are in standby mode, the operation fails sometimes. This issue is resolved in vCloud Director 5.5.2.1.

  • Unable to select storage policy when importing a virtual machine from vCenter into an existing vApp
    When you import a virtual machine from vCenter Server into an existing vApp, there is no option to select a storage policy for the virtual machine. This issue is resolved in vCloud Director 5.5.2.1.

  • Virtual machines configured with static IP from a pool sometimes obtain IP addresses through DHCP after the pool is exhausted
    In some cases, virtual machines configured to obtain a static IP address from a pool still obtain addresses through DHCP after the pool is exhausted. This issue is resolved in vCloud Director 5.5.2.1.

vCloud API Issues

  • Using the vCloud API or SDK to create a user sometimes results in an error message
    When you create a new user in an organization by using the vCloud API or SDK after that user has been imported to other organizations in the cloud, vCloud Director creates the user, but displays an error message. This issue is resolved in vCloud Director 5.5.2.1.

Known Issues

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

The known issues are grouped as follows:

General Issues

  • Attempts to upload or download an OVF or configure joint IPSEC VPN might fail
    When you try to use the vCloud Director Web Console in the Google Chrome browser to perform an OVF upload or download operation, or configure joint IPSEC VPN, a message might appear saying that the operation is not supported in your browser.

    As of this version of vCloud Director, using the vCloud Director Web Console to perform the operations to upload or download OVFs or to configure joint IPSEC VPN is not supported in the Google Chrome browser.

    Workaround: To perform OVF upload or download operations, use the VMware OVF Tool. The OVF Tool and its User Guide are available on the OVF Tool Documentation page.

    Instead of configuring IPSEC VPN jointly, configure them separately. See Create a VPN Tunnel to a Remote Network.

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

  • vCloud Director does not display a datastore cluster after adding new datastores to the cluster
    After you add one or more datastores without user-defined storage capability to a datastore cluster, the vCloud Director Web console does not display the datatsore cluster. When this occurs, vCloud Director displays an alert on the provider virtual datacenter.

    Workaround: To clear the alert, sign in to vCenter Server and manually assign user-defined storage capability to the datastores.

Installation and Upgrade Issues

  • Database upgrade error message when you upgrade to vCloud Director 5.5.2
    When you upgrade vCloud Director to version 5.5.2 by using an MS SQL database, the following error message appears.

    Unable to update database statistics. Database user has insufficient privileges to update database statistics. To complete this step manually, run 'EXEC sp_updatestats' as the DBO or a member of the sysadmin fixed server role.

    Workaround: As a database administrator, run the command EXEC sp_updatestats on the database.

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

    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.

  • vCloud Director displays some catalogs' status as Unknown after you upgrade vCloud Director from version 5.1.x
    After you upgrade vCloud Director from version 5.1.x, vCloud Director displays the status of some catalogs that were present before the upgrade as Unknown and displays those catalog names highlighted in gray. This issue occurs when the catalog has existed for longer than the activity log of vCloud Director, and the task might have been deleted from the database resulting in a catalog status of unknown.

    After you upgrade to vCloud Director 5.5.2, the Status column for catalogs is not displayed by default. You can display catalog columns by clicking Customize Columns and selecting Status.

    Workaround: This issue has no workaround, but you can reduce the probability of an unknown status appearing by extending the activity log for tasks in vCloud Director.

    1. Log in to vCloud Director as a System Administrator.
    2. Click Administration.
    3. Click General and click Activity Log.
    4. Update the number of days to keep to 365.

    Days to keep nominally increase in size when increased in the database.

Localization Issues

  • A virtual machine's popped-out console displays a blank screen with disconnected status when using the Google Chrome or Mozilla Firefox browsers and the virtual machine's name uses non-ASCII characters
    When you are using the Google Chrome or Mozilla Firefox browser and you pop out a virtual machine's console from the vCloud Director Web Console, the console might display a black screen and disconnected status if the virtual machine's name contains non-ASCII characters.

    Workaround: Use Microsoft Internet Explorer browser to open the virtual machine's console.

  • 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 or DVD device name containing non-ASCII characters causes attempts to add the CD or 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 or 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 virtual machine.

Virtual Machine and vApp Issues

  • vApp NAT and Firewall cannot be modified by a vApp Author deploying the vApp
    When you deploy a vApp from a catalog as a vApp author using the vCloud Director Web console, the NAT and Firewall check boxes in the Advanced Networking setup are disabled.

    Workaround: After the vApp is deployed, you can modify the NAT and Firewall settings for the vApp.

  • Windows Server 2008, 2008 R2, and 2012 virtual machines ask you to reset the guest operating system password after you customize the virtual machine with SID change
    When you power on a Windows Server 2008, 2008 R2, or 2012 virtual machine after customizing the virtual machine with SID change and do not customize the virtual machine to reset the password, the guest operating system asks you to reset the password.

vCloud API Issues

  • Load balancer pools cannot be modified on an individual basis using the vCloud API
    Currently you cannot add, remove, or edit a load balancer pool by using the vCloud API. Modifications made to one load balancer pool by using the vCloud API affect all load balancer pools.

  • Attempts to delete a metadata key using the vCloud API fail if the value of the metadata Key element, the key name, contains an ampersand (&)
    When a metadata key name contains an ampersand (&), attempts to delete the metadata using the vCloud API fail unless the deletion link is parsed to replace the reserved character with its percent-encoded representation.

    Workaround: Use the vCloud Director user interface to delete metadata where the key name contains an ampersand.