VMware

vCloud Director 5.5.1 Release Notes

vCloud Director 5.5.1 | 11 MAR 2014 | Build 1654672

Last updated: 12 FEB 2015

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Increased platform operating system support: vCloud Director has added support for the following platform operating systems.
    • Red Hat Enterprise Linux 5.10
    • Red Hat Enterprise Linux 6.5
  • Increased guest operating system support: vCloud Director has added support for the following guest operating systems.
    • Red Hat Enterprise Linux 5.10
    • Red Hat Enterprise Linux 6.5
    • SUSE Linux Enterprise Server 11 with service pack 3
    • Ubuntu 13.10
    • Ubuntu 12.0.4.3
    • Windows 8.1 32-bit
    • Windows 8.1 64-bit
    • Windows Server 2012 R2
  • 64-bit guest customization: Guest customizations now run as 64-bit on the following 64-bit guest operating systems.
    • Windows 8.1
    • Windows 8
    • Windows Server 2012
    • Windows Server 2012 R2
    • Windows 2008
    • Windows 2008 R2
  • Updated Java Runtime Environment version: vCloud Director 5.5.1 uses Java Runtime Environment 1.7 update 25.

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.1 documentation, go to the vCloud Director Documentation page.

Resolved Issues

This release resolves issues in the following areas.

General Issues

  • Blocking tasks might stop responding even if approved if the approval originated on a different cell than the one that started the task
    In a multi-cell vCloud Director installation, blocking tasks originating on one cell cannot be handled (approved or denied) by another cell and stop responding unless the originating cell is identified and an approval created there. This issue is resolved in vCloud Director 5.5.1.

  • Incorrect error message when attempting to upload an OVF package that includes a mounted ISO file
    Attempts to upload an OVF package that includes a mounted ISO file must fail with an error message indicating that you cannot upload an OVF package that includes a reference to another file. Instead, the upload results in an error similar to the following.

    Internal Server Error - Broken Pipe

    This issue is resolved in vCloud Director 5.5.1.

  • No right to restrict uploading or downloading OVF files in My Cloud
    vCloud Director does not have a separate right to restrict uploading or downloading OVF files in My Cloud. vCloud Director 5.5.1 adds two new rights: Download a vApp and Upload a vApp.

  • Attempting to interact with a shared catalog fails with a no access to entity error
    When you attempt to interact with a catalog that is shared with All organizations from a different organization than the one you are working in, vCloud Director displays the error No access to entity. This issue is resolved in vCloud Director 5.5.1.

  • vCloud Director sometimes lists datas tores added to vCenter Server as inaccessible
    New data stores added to vCenter Server are sometimes listed as inaccessible in vCloud Director. This issue is resolved in vCloud Director 5.5.1.

  • Data stores deleted in vCenter Server sometimes continue to appear in vCloud Director
    Deletion in vCenter Server of a data store used by vCloud Director could leave stale entries in the vCloud Director database. This issue is resolved in vCloud Director 5.5.1.

  • Attempts add ISO files from another organization fail
    When you attempt to add an ISO file from another organization, the operation fails with the error BadRequestException: This media type is incorrect. This issue is resolved in vCloud Director 5.5.1.

  • Task returned by a vdcCaptureTemplate operation does not contain certain elements
    When you enable vdcCaptureTemplate as a blocking task, the Params element of the blocking task created does not include values for name, Description, and TargetCatalogItem. This issue is resolved in vCloud Director 5.5.1.

  • ISO files uploaded to vCloud Director are sometimes placed in deep, recursive directory structures
    On systems where uploaded ISO files were typically placed in a directory structure similar to the following:

    /vmfs/volumes/datastore_1/vdc01/media/{id1}/{id2}/media-{id3}.iso/media-{id4}.iso

    ISO uploads could sometimes be placed in an unnecessarily deep directory structure similar to the following:

    /vmfs/volumes/datastore_1/vdc01/media/vdc01/media/vdc01/media/vdc01/media/vdc01/media/vdc01/media/vdc01/media/{id1}/{id2}/media-{id3}.iso/media-{id4}.iso

    This issue is resolved in vCloud Director 5.5.1.

  • Incorrect catalog item ownership
    Ownership of items in catalogs is assigned to the user who created the catalog, typically the system administrator, rather than the user who added the item to the catalog. This issue is resolved in vCloud Director 5.5.1.

  • Hostname validation fails for hostnames that begin with a number
    When attempting to register or update a vCenter server whose hostname begins with a number (for example, 9thfloor.example.com), vCloud Director might fail the registration or update and log an error similar to the following.

    validation error on field 'vshieldManagerSpec.url.host': String value has an invalid format
    validation error on field 'vimServer.url.host': String value has an invalid format

    This issue is resolved in vCloud Director 5.5.1.

Installation and Upgrade Issues

  • Error during installation or upgrade when using Microsoft SQL Server 2005 SP4
    Attempts to install or upgrade to vCloud Director 5.5 using SQL Server 2005 SP4 as the vCloud Director database might fail with an error message similar to the following.

    Exception in thread "main" java.lang.IllegalStateException: java.sql.SQLException: Cannot assign a default value to a local variable.

    This issue is resolved in vCloud Director 5.5.1.

  • Shadow VMs cannot be deleted after upgrading vCloud Director
    After the upgrade, you cannot create new shadow VMs in the same folder that holds legacy shadow VMs created before the upgrade, making it impossible to delete the legacy shadow VMs. This issue is resolved in vCloud Director 5.5.1.

Networking Issues

  • Edge gateway properties can take a long time to load
    The higher the number of external networks associated with an Edge gateway, the longer it takes the vCloud Director web client to load the properties page for the Edge gateway. This issue is resolved in vCloud Director 5.5.1.

  • No network connection after changing a virtual machine's CPU or memory
    If you shut down the guest operating system of a virtual machine and then modify the VM's CPU or memory settings, the VM loses its network connection when you power it on again. This issue is resolved in vCloud Director 5.5.1.

Virtual Machine and vApp Issues

  • Internal server error when deploying linked clones
    Deployment of vApps sometimes fail with an internal server error in an organization virtual datacenter that supports fast provisioning and is backed by a data store that is VAAI-enabled. This issue is resolved in vCloud Director 5.5.1.

  • Add to My Cloud sometimes failed
    Add to My Cloud operations sometimes fail for administrators and users even though they have rights to deploy vApps. This issue is resolved in vCloud Director 5.5.1.

  • Administrators unable to view vApp networks in vApps they do not own
    Organization and system administrators are sometimes unable to view a vApp network in a vApp that they do not own. This issue is resolved in vCloud Director 5.5.1.

  • Attempts to migrate multiple vApps at once might cause vApp ownership to change to system
    When you migrate multiple vApps from one organization virtual datacenter to another, ownership of the vApps sometimes changes to system, making it impossible to determine the ownership of the vApps. This issue is resolved in vCloud Director 5.5.1.

  • Attempts to copy a virtual machine from a catalog to a catalog that uses a different storage policy fail
    When you attempt to copy a virtual machine from a catalog using one storage policy to a catalog using a different storage policy, the operation fails. This issue is resolved in vCloud Director 5.5.1.

  • Guest customization script gets corrupted when you compose a vApp from a catalog
    When you use the vCloud API or vCloud Director Web client to compose a vApp from a catalog, the guest customization script for the new vApp is corrupted. This issue is resolved in vCloud Director 5.5.1.

  • Uploading a vApp or media file sometimes fails
    Attempting to upload a vApp or media file failed with the error Target SSL fingerprint mismatch detected if the vCloud Director DNS name includes cloud. This issue is resolved in vCloud Director 5.5.1.

  • CPU and memory information not reported correctly
    For virtual machines imported into a vApp, vCloud Director does not set values for the virtual machines' CPU and memory in vCloud Director audit events. As a result, no CPU and memory information for those VMs are available to VMware vCenter Chargeback. This issue is resolved in vCloud Director 5.5.1.

  • Storage used by virtual machine snapshots sometimes went undetected by vCenter Chargeback Manager
    At vCloud Director sites where vCenter Chargeback Manager is in use, storage consumed by a virtual machine snapshot is not added to the storage consumed by the virtual machine itself for chargeback purposes. This issue is resolved in vCloud Director 5.5.1.

  • Specifying a new storage policy for a virtual machine might cause the new storage policy to exceed its limit
    When a virtual machine is relocated to a new storage policy, the operation sometimes succeeds even though it causes the new storage policy to exceed its specified storage limit. This issue is resolved in vCloud Director 5.5.1.

  • Guest customization triggered after you edit virtual machine properties
    Editing any virtual machine property might cause guest OS customization to be triggered at the next reboot of that virtual machine. This issue is resolved in vCloud Director 5.5.1.

  • Relocating a linked clone template can cause a snapshot error in subsequent deploy attempts
    After relocating a vApp template from a VDC enabled for fast provisioning to a different data store, attempts to instantiate the template fail with an error similar to the following.

    Managed object of type "VirtualMachineSnapshot" with value "nnn" does not exist.
    vCenter Server task (moref: task-nnn) failed in vCenter Server 'server_name' (nnn)

    This issue is resolved in vCloud Director 5.5.1.

  • No IP address displayed for some virtual machines with only IPv6 addresses
    In some cases, when a virtual machine is created with only IPv6 addresses and no IPv4 address, no IP address of either type is shown for that virtual machine. This issue is resolved in vCloud Director 5.5.1.

vCloud API Issues

  • Ability to change the capacity of a storage profile to an incompatible value
    It iss possible to use the vCloud API to change the capacity of an AdminVdcStorageProfile with allocation model ALLOCATION_POOL to an invalid value such as unlimited or a value less than what is already consumed. Doing so can cause several problems for users of the vCloud Director Web Console, including making it impossible to change the capacity of the storage profile.

    This issue is resolved in vCloud Director 5.5.1.

  • Incorrect XML returned for an EdgeGateway entity
    When invoked by a user who does not have the Administrator Control right, the vCloud API entity resolver does not return correct XML for an EdgeGateway entity. This issue is resolved in vCloud Director 5.5.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

  • 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

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