vCloud Director 5.5.5 Release Notes

Updated on: 22 OCT 2015

vCloud Director 5.5.5 | 22 OCT 2015 | Build 3153714

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Upload and download of OVF and Media supported in the Chrome browser: vCloud Director 5.5.2.1 removed support for uploading or downloading OVF or media files when running the vCloud Director Web Console in the Chrome browser. This release removes that restriction on Windows and Mac platforms.

    Installing this release of vCloud Director has the following effects on Windows clients that run the vCloud Director Web Console in Chrome:

    • On the first attempt to upload or download an OVF or Media file, the system prompts you to download and install a new version of the vCloud Director Client Integration Plug-In (VMware-ClientIntegrationPlugin-5.6.0.exe).
    • The download also installs a new service, vmware-csd.exe, that runs on the client machine to support OVF and Media file upload and download.

    Uploading and downloading OVF or media files when running the vCloud Director Web Console on Linux operating systems is still restricted. To upload or downlad an OVF or media file on a Linux operating system, use Mozilla Firefox to acces the vCloud Director Web Console.

System Requirements and Installation

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

For Windows operating systems, the Client Integration Plugin version 5.6.0 is supported only on Windows Vista or later. If you are using an earlier version of Windows, you cannot upload or download OVF or media files using a Google Chrome browser.

Documentation

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

Resolved Issues

This release resolves the following issues.

General Issues

  • vCloud Director displays an eleasticity related error message when you modify any of the system settings
    When you modify any of the settings on the General Settings page when the allocation pool elasticity setting is already disabled, vCloud Director sometimes displays the following error message.

    Cannot turn off elasticity for Allocation Pool OrgVdcs.
    All the Allocation Pool OrgVdcs cannot be accommodated on the primary cluster of their PVDCs.

    This issue is resolved in vCloud Director 5.5.5.

Networking Issues

  • Attempts to upload or download an OVF or media file over a network proxy service fail
    When you attempt to upload or download an OVF or media file in vCloud Director from a system that uses a network proxy service, the operation fails. This issue is resolved in vCloud Director 5.5.5.

Virtual Machine and vApp Issues

  • New virtual machines on an organization virtual data center using a resource pool allocation model sometimes fail to power on
    When you create a new virtual machine on an organization virtual data center using a resource pool allocation model that is backed by a provider virtual data center with multiple resource pools, vCloud Director sometimes incorrectly places the new virtual machine on a secondary resource pool. When you attempt to power on the new virtual machine, the operation fails with an error similar to the following.

    Unable to start vApp "vApp1".
    - The operation could not be performed, because there are insufficient memory resources.
    vCenter Server task (moref: task-449) failed in vCenter Server 'vc1' (04ddf181-c981-469e-80fe-cfe9adb9d84b).
    - The available Memory resources in the parent resource pool are insufficient for the operation.

    This issue is resolved in vCloud Director 5.5.5.

  • 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. This issue is resolved in vCloud Director 5.5.5.

  • Attempts to modify a virtual machine description fail when the description is longer than one line
    When you attempt to modify a virtual machine description with a description that is longer than a single line of text, the operation fails with the following error.

    VM description cannot contain control characters

    This issue is resolved in vCloud Director 5.5.5.

  • Attempts to power on a vApp backed by a non-elastic Allocation Pool organization virtual data center sometimes fail
    If the provider virtual data center backing an organization virtual data center configured with an Allocation Pool allocation model with elasticity disabled does not have the resources to power on a vApp, attempts to power on the vApp fail even though the organization virtual data center has the resources to power on the vApp. When this occurs, vCloud Director displays the following error message.

    The operation failed because no suitable resource was found. Hub "XXXXX" doesn't meet compute requirement:
    CpuMHzMin:1000, mandatory:true, checkMinHostCapacity:false.

    This issue is resolved in vCloud Director 5.5.5.

API Issues

  • vCloud API query fails to return the port group name for port groups backed by a VXLAN network
    When you run the following vCloud API query for a port group backed by a VXLAN network, vCloud Director does not return the port group name.

    GET https:///api/query?type=portgroup&format=records

    This issue is resolved in vCloud Director 5.5.5.

Known Issues

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

General Issues

  • Google Chrome does not display ISO images when you attempt to upload an ISO image from a local file to vCloud Director
    When you attempt to browse for an ISO image to upload from a local file in My Organizaion, vCloud Director does not display ISO images by default.

    Workaround: Select All Files from the Files of type drop-down menu. The ISO image appears with a question mark icon.

  • Attempts to download an OVF fail if an OVF of the same name already exists in the target download location
    When you attempt to download an OVF that has the same file name as another OVF already present in the target download location, the download fails at 0%.

    Workaround: ype a new name for the OVF in the download dialog box.

CSD Issues (new feature)

  • Attempts to upload an OVF or OVA from a URL in My Cloud as a vApp sometimes fail
    When you attempt to upload an OVF or OVA from a URL in My Cloud as a vApp, the operation sometimes fails with the following error.

    cURL error: Couldn't connect to server

    Workaround: Upload the file from a local datastore or add it as a vApp template.

    Upload the OVF/OVA file from a local datastore.

    1. Download the OVF/OVA file to a local datastore.
    2. In My Cloud, select Add vApp from OVF.
    3. Select Local File, and click Browse.
    4. Navigate to the OVF/OVA file location on the local datastore, and click OK.
    5. Review the details of the uploaded OVF and click Next.
    6. Type a name and optional description for the vApp.
    7. Select a virtual datacenter on which to store and run the vApp from the drop-down menu and click Next.
    8. Select a storage policy for the vApp's virtual machines from the drop-down menu and click Next.
    9. Select the network for the virtual machines to connect to from each virtual machine's drop-down menu and click Next.
    10. Review the hardware settings for the virtual machines in the vApp and optionally change those configurations.
    11. Click Next.
    12. Review the vApp's configuration and click Finish.

    Upload the OVF/OVA as a vApp template.

    1. Click Catalogs > My Organization's Catalogs.
    2. On the vApp Templates tab, click the Upload button.
    3. Type the name and path of the OVF file to upload, and click Upload.
    4. Type a name and optional description for the vApp template.
    5. Select a destination virtual data center and catalog.
    6. Click Upload.
    7. After the upload finishes, click My Cloud > vApps.
    8. Click the Add vApp from Catalog button.
    9. Select My organization's catalogs from the drop-down menu.
    10. Select the vApp template you created from the OVF/OVA file and click Next.
    11. Type a name and optional description for the vApp.
    12. Select a runtime and storage lease and click Next.
    13. Select a virtual datacenter, configure the virtual machines in the vApp, and click Next.
    14. Configure the custom properties, if any, and click Next.
    15. Configure the networking options for the vApp and click Next.
    16. Review the vApp summary information and click Finish.

  • vCloud Director displays an error when you access vCloud Director using Mozilla Firefox or Google Chrome after uninstalling the Client Integration Plugin version 5.6
    When you attempt to access vCloud Director using Mozilla Firefox or Google Chrome after you uninstall the Client Integration Plugin version 5.6, vCloud Director displays the following error.

    No apps are installed to open this type of link (vmware-csd)

    Workaround: Click anywhere in the browser to dismiss the error message. This error does not impact vCloud Director functionality. The error message stops appearing if you reinstall the Client Integration Plugin version 5.6.

  • Google Chrome fails to detect the Client Integration Plugin after vCloud Director user login session timeout
    When you attempt to upload or download an OVF, OVA, or media file on a Google Chrome browser after your vCloud Director user login session times out, Chrome fails to detect the Client Integration Plugin and asks you to download the Client Integration Plugin again.

    Workaround: Open vCloud Director in a new tab in Chrome and retry the operation.

Localization and Globalization Issues

  • Attempts to install the Client Integration Plugin version 5.6 might fail for Windows user names that contain non-ASCII characters
    When you attempt to install the Client Integration Plugin version 5.6 on a Windows operating system with a user name that contains non-ASCII characters, the installation might fail.

    Workaround: Install the Client Integration Plugin version 5.6 using a Windows user name that contains no non-ASCII characters.

  • Client Integration Plugin version 5.6 displays Traditional Chinese user interface on operating systems using Simple Chinese
    When you install and use the Client Integration Plugin version 5.6 on an operating system with its language set to Simple Chinese, vCloud Director displays Traditional Chinese in the Client Integration Plugin user interface.

  • Media file names that contain non-ASCII characters as garbage characters after you download the file on a Mac OS
    After you download a media file with a name that contains non-ASCII characters to a Mac operating system, the operating system displays the media file name as garbage characters.

  • vCloud Director incorrectly prompts you to install the Client Integration Plugin on Mac operating systems using a double-byte language
    When you attempt to download a media file on a Mac operating system using a double-byte language, such as Japanese or Simplified Chinese, vCloud Director prompts you to install the Client Integration Plugin even when the plugin is already installed.

  • 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.4, the host agent upgrade fails.

    Workaround: Unprepare the host to remove the host agent, then prepare the host agent again.

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

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

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

  • vSphere SSO users whose user names include non-ASCII characters cannot log in to vCloud Director after they are imported
    When a user defined by the vSphere SSO service has a user name that includes non-ASCII characters, the user name is not decoded correctly when the imported user logs into the system, resulting in log in failure. This issue occurs only when you use vCloud Director with vSphere 6.0.

    Workaround: Change usernames to use only ASCII characters before using vSphere SSO to import users.

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.