VMware

vCloud Director 5.5.2 Release Notes

vCloud Director 5.5.2 | 9 SEP 2014 | Build 2000523

Last updated: 12 FEB 2015

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Increased database support: vCloud Director has added support for the following external databases.
    • Oracle Database 12c
    • SQL Server 2014
  • Increased LDAP provider support: vCloud Director has added support for Windows 2012 as an LDAP provider.
  • Increased platform operating system support: vCloud Director has added platform operating system support for CentOS 6.5.
  • Increased guest operating system support: vCloud Director has added support for the following guest operating systems.
    • Red Hat Enterprise Linux 7
    • Ubuntu 14.04
    • SUSE Linux Enterprise Server 12
    • CentOS 6.5
    • CentOS 7
    • Oracle Linux 6.5
    • Oracle Linux 7
  • Increased guest operating system customization support: vCloud Director has added customization support for the following guest operating systems.
    • Red Hat Enterprise Linux 7
    • Ubuntu 14.04
    • SUSE Linux Enterprise Server 12
    • CentOS 6.5
    • Oracle Linux 6.5
  • Updated Java Runtime Environment version: vCloud Director 5.5.2 uses Java Runtime Environment 1.7 update 55.

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. To upgrade to vCloud Director for Service Providers after you upgrade to vCloud Director 5.5.2, 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 issues in the following areas.

General Issues

  • The fix-scheduler-data command is not displayed on the cell-management-tool help page
    The fix-scheduler-data command for the cell-management-tool fixes Quartz scheduler data. This command is not displayed on the cell-management-tool help page. This issue is resolved in vCloud Director 5.5.2.

  • Datastores are inaccessible after being moved to storage pods
    After you move a datastore to a storage pod in vCenter Server, the datastore is inaccessible from vCloud Director. This issue is resolved in vCloud Director 5.5.2.

  • Provider virtual datacenter sometimes loses access to datastores and storage pods after moving a datastore into or out of a storage pod
    When you move a datastore into or out of of a storage pod, the provider virtual data center using the pod might lose access to the datastore or pod. This issue is resolved in vCloud Director 5.5.2.

  • vCloud Director displays incorrect CPU used for elastic Allocation Pool organization virtual data centers
    When an elastic Allocation Pool organization virtual datacenter is backed by multiple resource pools and the percentage of resources guaranteed for the organization virtual data center is changed, the vCloud Director Web console displays an incorrect CPU Total Allocated Capacity for organization virtual data centers. This issue is resolved in vCloud Director 5.5.2.

  • Load balancer configuration changes sometimes do not appear in vCloud Director
    When you change the load balancer configuration at the same time that you edit the load balancer in the vCloud Director Web console, vCloud Director does not record the changes to the load balancer configuration, and the load balancer configuration appears different in vCloud Director than it does in vShield Manager. This issue is resolved in vCloud Director 5.5.2.

  • Users with the right to add a template to a catalog cannot overwrite a template unless they have the right to edit a catalog enabled
    When a user has the right to add a template to a catalog enabled, the user can only overwrite an existing template if they also have the right to edit a catalog enabled. This issue is resolved in vCloud Director 5.5.2.

Networking Issues

  • Edge gateways displayed for an external network when the network is not connected to Edge gateways
    When you click the Gateways tab for an external network that is not connected to Edge gateways, the vCloud Director Web console displays all Edge gateways on the system. This issue is resolved in vCloud Director 5.5.2.

  • vCloud Director does not allow you to reuse IP addresses that are no longer in use in the sub allocation pool of an Edge gateway
    When you try to assign an IP address that was previously used by a virtual machine to the sub allocation pool of an Edge gateway, the operation fails with an error message stating that the IP address is already in use. This issue is resolved in vCloud Director 5.5.2.

  • vCloud Director does not validate the load balancer virtual server IP when the load balancer is added through service insertion
    When you add a load balancer using service insertion, vCloud Director does not validate the virtual server IP of the load balancer. In vCloud Director 5.5.2, you can enable validation using a configuration parameter.

  • Trying to assign a NAT IP to a vApp routed network set to manual fails
    When you try to assign a NAT IP to a vApp routed network with a NAT rule set to manual, the operation fails with the following error message.

    Invalid IP address for external network

    This issue is resolved in vCloud Director 5.5.2.

  • DCHP settings for a routed vApp network are not preserved when the parent network is modified
    When you modify the parent network of a routed vApp network, the DHCP settings of the routed vApp network are lost. This issue is resolved in vCloud Director 5.5.2.

  • Default gateway set for multiple virtual machine NICs after selecting Change SID during guest customization
    When you select Change SID during guest customization for a virtual machine with multiple NICs, vCloud Director assigns a default gateway to all NICs on the virtual machine instead of only on the primary NIC. This issue is resolved in vCloud Director 5.5.2.

  • Virtual machine network is re-customized after moving the virtual machine from one vApp to another
    After moving a virtual machine from one vApp to another vApp in the same organization, the virtual machine's network is re-customized when the virtual machine is powered on. This issue is resolved in vCloud Director 5.5.2.

Virtual Machine and vApp Issues

  • New virtual machines sometimes exceed the datastore limit when you deploy multiple new virtual machines simultaneously
    When you deploy multiple virtual machines at the same time, the combined size of the deployed virtual machines might exceed the datastore limit. This issue is resolved in vCD 5.5.2.

  • Virtual machines added from OVF in vCloud Director do not appear in Chargeback Manager
    When you add a vApp from OVF in vCloud Director, the virtual machine created does not appear in the virtual machines list in Chargeback Manager. This issue is resolved in vCloud Director 5.5.2.

  • Attempting to set a deployment lease during vApp creation fails
    When you set a deployment lease value during vApp creation, the deployment lease value is not preserved in the new vApp. This issue is resolved in vCloud Director 5.5.2.

  • vCloud Director does not display the runtime lease of a vApp in a partially powered off state
    When a vApp is partially powered off, the vCloud Director Web console does not display the runtime lease for the vApp. This issue is resolved in vCloud Director 5.5.2.

  • Virtual machine time zone set to GMT after Change SID
    When you select Change SID for a virtual machine, the virtual machine time zone is changed to GMT. This issue is resolved in vCloud Director 5.5.2.

  • Disconnecting a NIC from the virtual machine properties page of the vCloud Director Web console fails
    When you deselect the Connected check box on a virtual machine's Properties page using the vCloud Director Web console, the NIC remains connected. This issue is resolved in vCloud Director 5.5.2.

  • vCloud Director does not display some organization virtual data center networks during direct vApp network creation
    When you create a direct vApp network by using the vCloud Director Web console, vCloud Director does not display some available organization virtual data center networks. This issue is resolved in vCloud Director 5.5.2.

  • Properties missing in virtual machines deployed from an OVA template
    If you import a virtual machine into vCloud Director from an OVA template, some of the virtual machine properties are lost and do not appear in the imported virtual machine. This issue is resolved in vCloud Director 5.5.2.

  • Access forbidden error message when attempting to access a shared vApp template
    When you attempt to access a vApp template shared from another organization in vCloud Director, vCloud Director displays an access forbidden error if the source organization downloaded the vApp template by subscribing and syncing to an external catalog. This issue is resolved in vCloud Director 5.5.2.

  • Virtual machine has an incorrect name after syncing to a published catalog
    When you sync a vApp containing a single virtual machine to a published catalog, the virtual machine in the destination catalog is renamed to match the name of the vApp. This issue is resolved in vCloud Director 5.5.2.

  • vApp template stop action is not preserved after export from and import into vCloud Director
    When you import a vApp template that was previously exported from vCloud Director, the template's stop action is not preserved in the imported vApp template. This issue is resolved in vCloud Director 5.5.2.

  • 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 and password reset
    When you power on a Windows Server 2008, 2008 R2, or Windows 2012 virtual machine after customizing the virtual machine with SID change and password reset, the guest operating system asks you to reset the password. This issue is resolved in vCloud Director 5.5.2.

  • Autologon for non-administrator incorrectly disabled
    When you have a virtual machine with a Windows operating system in which you have configured a non-administrator user to have the autologon feature enabled, and then you use the vCloud Director user interface or the vCloud API to customize the virtual machine's guest operating system properties and don't enable autologin for administrator, the autologon setting for the non-administrator user is incorrectly disabled. This issue is resolved in vCloud Director 5.5.2.

  • vCloud Director incorrectly displays a disk size of 4 MB for virtual disks larger than 2 TB
    When you add a virtual disk larger than 2 TB, the vCloud Director displays the disk size as 4 MB. This issue is resolved in vCloud Director 5.5.2.

  • Attempting to power on a vApp or a virtual machine created on a storage cluster might fail
    When you attempt to power on a virtual machine or vApp created on a storage cluster in an organization virtual data center that is thin provisioned with storage DRS disabled, the operation sometimes fails with the following error message.

    One or more exceptions have occurred - Unable to perform this action.
    Contact your cloud administrator.

    This issue is resolved in vCloud Director 5.5.2.

  • vCloud Director always lists the installed version of VMware Tools as the current version
    vCloud Director refers to the installed version of VMware Tools as the current version even a newer version of VMware Tools is available. This issue is resolved in vCloud Director 5.5.2.

vCloud API Issues

  • vCloud API does not display shared catalogs
    When you browse catalogs by using the vCloud API, shared catalogs and their contents are not displayed. This issue is resolved in vCloud Director 5.5.2.

  • Description field in NatRuleType is not recognized by vCloud Director
    When you set a description in NatRuleType for an Edge gateway NAT by using the vCloud API, vCloud Director does not record the description. This issue is resolved in the vCloud API for vCloud Director 5.5.2. vCloud Director 5.5.2 also allows you to use the vCloud Director Web console to assign descriptions to SNAT and DNAT rules created at the organization virtual data center level of gateways.

  • Attempts to delete a metadata key by using the vCloud API fail if the value of the metadata key element, the key name, contains a colon (:)
    Metadata key names containing colons can be entered in the vCloud Director user interface. However, when using the vCloud API to delete the metadata key that has a colon in its name, the attempt fails. This issues is resolved in vCloud Director 5.5.2.

  • Responses to vCloud API requests that involve catalog objects take a long time and sometimes time out
    The time for the vCloud API to construct a response to a call that involves catalog objects increased in vCloud Director 5.5. As a result, clients using such API calls might experience timeouts before the system returns the response to the client. This issue is resolved in vCloud Director 5.5.2.

  • Virtual machine network connectivity lost after modifying vApp lease properties by using the vCloud API
    After modifying vApp lease properties by using the vCloud API, virtual machines inside that vApp temporarily lose network connectivity. This issue is resolved in vCloud Director 5.5.2.

  • Request to capture a vApp as a template by using vCloud API fails
    When using vCloud API version 5.1 to capture a vApp as a template, the request fails if the organization does not include any catalogs that are not published. When using vCloud API version 5.1 with vCloud Director 5.5.2, published catalogs are considered for use by a captureVApp operation.

  • Attempting to retrieve an OrgVdc by using the vCloud API as a vApp user fails
    When you are signed in to vCloud Director as a vApp user and attempt to retrieve an OrgVdc by using the vCloud API, the operation fails with an Internal Server Error message. This issue is resolved in vCloud Director 5.5.2.

  • Attempting to move a virtual machine from a vApp template by using the relocate action API call fails
    When you use the deprecated relocate action API call to move a virtual machine from a vApp template, a Java null value exception about the cvmID value occurs and the relocate action fails. This failure typically occurrs for vApp templates that have been directly imported into vCloud Director.

    This issue is resolved in vCloud Director 5.5.2.

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.

  • 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

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