vCloud Director 5.5.6.1 Release Notes

Updated on: 17 MAY 2016

vCloud Director 5.5.6.1 | 17 MAY 2016 | Build 3814538

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

The Oracle (Sun) JRE package is updated to version 1.7.0_101. The update addresses a deserialization issue found in the RMI server of the Oracle (Sun) JRE JMX component. The Common Vulnerabilities and Exposures project has assigned CVE-2016-3247 identifier for this issue.

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

The following issues are resolved in this release of vCloud Director.

  • Cross-host settings are sometimes not applied to an ESX host after a reboot
    When an ESX host reboots, vCloud Director sometimes fails to apply cross-host settings to the host. This issue is resolved in vCloud Director 5.5.6.

  • vCloud Director audit event incorrectly displays a failure status when you modify an existing vApp
    When you modify an existing vApp and the CPU and memory updates succeed, but the storage update fails, the audit event displays a failure status. This issue is resolved in vCloud Director 5.5.6.

  • vApp instantiation audit event displays incorrect values after you modify the CPU, memory, or storage of the virtual machine when you add the vApp to My Cloud
    When you add a vApp to My Cloud from a vApp template and modify the CPU, memory, or storage of the virtual machine, vCloud Director does not display the modified values in the instantiation audit event. This issue is resolved in vCloud Director 5.5.6.

  • Attempts to download a vApp template or media file larger than 100GB fail after an hour
    When you attempt to download a vApp template or media file larger than 100GB, the operation fails after an hour with an operation timed out error message. This issue is resolved in vCloud Director 5.5.6.

  • Attempts to access the vCloud API sometimes fail
    When you attempt to access the vCloud API, the operation sometimes fail with a 404 error. This issue is resolved in vCloud Director 5.5.6.

Known Issues

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

General Issues

  • vCloud Director incorrectly prompts you to install the client integration plugin when you attempt to upload or download OVF/OVA or media files using a Microsoft Internet Explorer 11 browser in enterprise mode
    When you attempt to upload or download an OVF/OVA or media file using Internet Explorer on a Windows 7 or Windows 2008 operating system, vCloud Director prompts you to install the new client integration plugin even when the client integration plugin has already been installed.

    Workaround: Use Internet Explorer 11 in compatibility view mode to upload or download OVF/OVA or media files.

  • 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 Organization, 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: Type a new name for the OVF in the download dialog box.

CSD Issues

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

Virtual Machine and vApp Issues

  • Attempts to access a virtual machine console using a Microsoft Internet Explorer 11 browser in enterprise mode fail to connect
    When you attempt to access a virtual machine console using Internet Explorer 11 in enterprise mode, the operation hangs in a connecting state.

    Workaround: Access the virtual machine console using Internet Explorer 11 in compatibility view mode.

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.