vCloud Director 5.6.5 for Service Providers Release Notes

vCloud Director 5.6.5 for Service Providers | 10 DEC 2015 | Build 3307437

Last updated: 16 DEC 2015

What's in the Release Notes

The release notes cover the following topics:

What's New in this Release

  • Microsoft Internet Explorer 11 support: vCloud Director 5.6.5 adds browser support for Microsoft Internet Explorer 11.

System Requirements, Installation, and Upgrade

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

For interoperability information, see Interoperability Matrix, Upgrade Path and Configuration Maximums.

Documentation

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

Resolved Issues

This release resolves issues in the following areas.

General Issues

  • vCloud Director incorrectly sends notification emails to all organization administrators
    vCloud Director sends notification emails to all organization administrators regardless of whether vCloud Director notification settings indicate they should. This issue is resolved in vCloud Director 5.6.5.

  • Active directory account details not imported from Microsoft Active Directory Federation Services
    When you attempt to create an active directory user or group in vCloud Director using Microsoft Active Directory Federation Services SAML authentication, vCloud Director does not import active directory account details from Active Directory Federation Services. This issue is resolved in vCloud Director 5.6.5.

  • Attempts to access media files sometimes fail
    When you attempt to access a media file in vCloud Director, the operation sometimes fails with an error message similar to the following.

    The VCD entity (com.vmware.vcloud.entity.media:xxxx) does not exist

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

  • PFS enabled when you redeploy an Edge gateway
    When you redeploy an Edge gateway with a PFS disabled in the VPN settings, PFS is enabled after the deployment operations completes. This issue is resolved in vCloud Director 5.6.5.

  • Attempts to update Edge firewall rules result in a timeout error
    When you attempt to update Edge firewall rules in vCloud Director, the operation times out. This occurs because the socket timeout for communication between vCloud Director and vShield Manager or NSX is hard coded as 30 minutes.

    vCloud Director 5.6.5 resolves this issue by allowing you to change the socket timeout value of an installed vCloud Director server. See Changing the socket timeout value of vCloud Director.

Virtual Machine and vApp Issues

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

  • Attempts to deploy vApps from a catalog onto SDRS enabled clusters fails
    When you attempt to deploy a vApp from a public catalog onto SDRS-enabled clusters, the operation fails with an error message similar to the following.

    invalidProperty = StoragePlacementSpec.podSelectionSpec.initialVmConfig[].disk[].diskId
    inherited from com.vmware.vim.binding.vmodl.fault.InvalidArgument: A specified parameter was not correct.

    This issue is resolved in vCloud Director 5.6.5.

  • Attempts to migrate a virtual machine to a different datastore after you change its storage policy fail
    When you attempt to migrate a virtual machine to a different datastore after you use vCloud Director to change the virtual machine's storage policy, the operation fails. This issue is resolved in vCloud Director 5.6.5.

  • CPU and memory limits are incorrectly applied to a virtual machine after copying or moving the virtual machine or instantiating a vApp template from a Pay-As-You-Go virtual data center to a Reservation Pool virtual data center
    When you copy or move a virtual machine or instantiating a vApp template from an organization virtual data center using a Pay-As-You-Go allocation model to an organization virtual data center using a Reservation Pool allocation model, vCloud Director incorrectly applies the CPU and memory limits to the virtual machine from the previous allocation model. This issue is resolved in vCloud Director 5.6.5.

vCloud API Issues

  • vCloud API returns a size of 0 for all snapshots
    When you use the vCloud API to obtain virtual machine snapshot information using the SnapshotSection call, the vCloud API incorrectly returns size=0. This issue is resolved in vCloud Director 5.6.5.

  • Attempts to use the vCloud API to update the DHCP service on a cloud isolated network fail
    When you attempt to update the DHCP service on a cloud isolated network by using the vCloud API, the task appears to complete, but the DHCP service remains unchanged. This issue is resolved in vCloud Director 5.6.5.

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.

  • Attempts to upload or download an OVF or configure joint IPSEC VPN on Google Chrome 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.

    Google Chrome no longer supports OVF upload/download due to the removal of the NPAPI support within Chrome.

    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.

  • Numeric overflow database error in vCloud Director when storage of an organization virtual data center exceeds 2048 TB
    If the storage of an organization virtual data center is 2048 TB or greater, the vCloud Director Web client might display a numeric overflow database error when you attempt to perform any of the following actions in vCloud Director.
    • View the Media list
    • Deploy a new vApp in an organization
    • Move a vApp to a different organization virtual data center
    • Add an object to a catalog
    • Upload an OVA, OVF, or media file in an organization

Localization Issues

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

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

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

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

Networking Issues

  • Attempts to use a network backed by a vCloud Network Isolation network pool fail
    When you attempt to use a network backed by a vCloud Network Isolation network pool, the operation fails. This occurs because new installations of vCloud Director no longer push the host agent to ESX by default.

    Workaround: After adding a vCloud Network Isolation network pool, re-prepare the hosts on vCloud Director.

    1. In the vCloud Director Web client, click the Manage & Monitor tab and click Hosts in the left pane.
    2. Right-click the host name and select Prepare Host.
    3. Type a user name and password and click OK.

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.

  • Attempts to power on a vApp in an allocation pool organization virtual data center when the provider virtual data center has multiple resource pools sometimes fail
    When you create an allocation pool organization virtual data center on a provider virtual data center that is attached to multiple resource pools, only virtual machines placed on the first resource pool can successfully power on.

    Workaround: Enable elastic allocation pools.

    1. In the vCloud Director Web client, click the Administration tab and click General in the left pane.
    2. Select Allow allocation pools to be elastic and click Apply.
  • Virtual machine usage graph displays an incorrect time stamp for the first data point
    The first data point on a virtual machine usage graph always displays a time stamp of between 20 seconds and five minutes before the second data point, regardless of when the first data point is actually collected.
  • Attempts to disconnect a NIC from a powered on virtual machine fail
    When you request a hot disconnect of a NIC by using the UI or API, the request fails with a message similar to the following.

    The attempted operation cannot be performed in the current state (Powered on).

vCloud API Issues

  • Deprecated Link element in an AdminOrg element
    Beginning with vCloud API version 5.6, the following Link, which is returned in an AdminOrg element, is deprecated.

    <Link
    rel="task:create"
    href="https://.../api/tasksList/{id}"
    type="application/vnd.vmware.vcloud.task"/>

    The value of the type attribute in this Link is incorrect. The Link will be removed in a future release of vCloud Director. Beginning with vCloud API version 5.6, a new Link with the correct type attribute is also returned in an AdminOrg element.

    <Link
    rel="task:create"
    href="https://.../api/tasksList/{id}"
    type="application/vnd.vmware.vcloud.task+xml"/>

    Client applications should replace references to the deprecated Link with references to its replacement.