vCloud Director 8.0.2 for Service Providers Release Notes

vCloud Director 8.0.2 for Service Providers | 4 OCT 2016 | Build 4348775

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 in this Release

  • JRE version update: vCloud Director 8.0.2 for Service Providers uses JRE version 1.7.0_111.

  • Increased NSX support: vCloud Director 8.0.2 for Service Providers supports NSX version 6.2.4.

  • Additional language support in WebMKS console: In addition to English, this release supports the following keyboard layouts:
    • Japanese
    • German
    • Portuguese
    • Italian
    • Spanish

System Requirements and Installation

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

See the VMware Product Interoperability Matrixes for product compatibility information.

Documentation

To access the full set of vCloud Director 8.0 for Service Providers documentation, go to the vCloud Director for Service Providers Documentation page.

Resolved Issues

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

General Issues

  • In vCloud Director 5.6.4, the WebMKS console stops responding intermittently when the console limit is set
    When you set the console limit to 1 in the Organization Properties, the VM console cannot be reopened immediately after it is closed.

    This issue is resolved in vCloud Director 8.0.2.

  • Intermittent failure of vCD vApp deployment
    When you attempt to deploy vApp either manually or through the vCO workflow, the deployment might fail with the following error:
    Could not find resource pool for placement of edge gateway.

    This issue is resolved in vCloud Director 8.0.2.

  • Downloading a large vApp template as an OVF file from the vCloud Director fails
    Attemps to download a large vApp template as an OVF file from vCloud Director fails due to an operation timeout error in both vCloud Director and vCenter Server. This issue is seen when the size of the vApp template is greater than 100 GB.

    This issue is resolved in vCloud Director 8.0.2.

  • The Cell Management Tool on vCloud Director 8.0 does not support the use of LDAP credentials
    The Cell Management Tool on vCloud Director 8.0 does not support the use of LDAP credentials.

    This issue is resolved in vCloud Director 8.0.2.

  • Changing the Storage Profile of a VM that has a snapshot fails with an error
    After upgrading to VDC 5.6.x, or 8.0.x, if you attempt to change the Storage Profile of a VM that has a snapshot, an error message similar to the following is displayed:
    Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1

    This issue is resolved in vCloud Director 8.0.2.

  • vCloud Director Cell uses a high percentage of the CPU
    The vCloud Director cell uses more than 90 percent of the CPU. As a result, the vCloud Director workload is affected.

    This issue is resolved in vCloud Director 8.0.2.

  • In the WebMKS console, the mouse pointer does not work when VMware tools are not installed in the Guest OS
    In the WebMKS console, the mouse pointer does not work when VMware tools are not installed in the Guest OS. To address the issue, the relative mouse functionality is introduced in this release.

    This issue is resolved in vCloud Director 8.0.2.

  • During a heavy load, vCloud Director can have two or more VMs that have the same CloudUUID in the system
    During a heavy load, vCloud Director can have two or more VMs with the same CloudUUID in the system. This causes the Managed Object Reference (moref) of the VM to be overwritten by another VM. Due to the duplicated CloudUUID, a wrong VM might get deleted.

    This issue is resolved in vCloud Director 8.0.2.

  • After a reboot, the cross host settings do not get pushed to the stateless ESXi host
    After a reboot, the cross host settings do not get pushed to the stateless ESXi host.

    This issue is resolved in vCloud Director 8.0.2.

Virtual Machine and vApp Issues

  • Duplicated VM is displayed in the vCloud Director UI when you create a vApp with an LDAP user imported to multiple orgs
    In vCloud Director 8.0, when you try to create a vApp with an LDAP user who is imported to multiple orgs, a duplicated VM is displayed in the vCloud Director UI - vmsListPage.

    This issue is resolved in vCloud Director 8.0.2.

  • Deletion of Orphan vApp Template, Media, or Independent disks fails with an error
    Deletion of Orphan vApp Template, Media, or Independent disks fails with the following error:
    Catalog Item not found

    This issue is resolved in vCloud Director 8.0.2.

  • In the latest Mac version (OS X El Capitan), the Upload, or Download dialog box does not close correctly
    After you update your system to the latest Mac version (OS X El Capitan), when you attempt to upload a file from the data store the Upload, or Download dialog box does not close correctly.

    This issue is resolved in vCloud Director 8.0.2.

  • vApp deployment from a template fails with certain direct organization VDC networks, when there are multiple direct organization VDC networks in a VDC that are mapped to the same external network
    When there are multiple direct organization VDC networks in a VDC that are mapped to a single external network, deploying a vApp from the template is possible with only one of these networks. The deployment fails when other networks are selected.

    This issue is resolved in vCloud Director 8.0.2.

  • VDC displays an incorrect system alert for a vApp that is deployed in a non-elastic Allocation Pool organization virtual data center
    VDC displays the following system alert for a vApp that is deployed in a non-elastic Allocation Pool organization virtual data center. The following alert is displayed even when the memory reservation of the virtual machine is not modified.
    System alert - VM memory reservation was modified

    This issue is resolved in vCloud Director 8.0.2.

API Issues

  • .NET API error prevents provisioning of new virtual data centers
    The .NET API VMWProviderVdc.GetVMWProviderVdcByReference() returns null, and prevents the provisioning of new virtual data centers.

    This issue is resolved in vCloud Director 8.0.2.

Networking Issues

  • Edge gateway fails to deploy when a create request is invoked from the vCloud Director cell that does not have a vCenter Server proxy listener
    In a multi-cell vCloud Director setup, the Edge gateway creation is successful only when the create request is invoked from the vCloud Director cell that has a vCenter Server proxy listener.

    This issue is resolved in vCloud Director 8.0.2.

Known Issues

The following localization issue is known to occur in this release of vCloud Director.

  • In the WebMKS console, some keys do not work in the non-English keyboard layouts
    The following keys in the non-English keyboard layouts are not mapped correctly in a virtual machine. When you press the following keys with non-English Windows or Mac keyboard, the keys might not work, or a wrong key might be entered in the WebMKS console.

    Japanese Windows Keyboard:
    • Application Key, PrtScrn, Scroll Lock, 半角/全角, 英数, 変換, 無変換, カタカナひらがな
    • \(ろ)when Kana is enabled

    German Windows Keyboard:
    • Application Key, PrtScrn, Scroll Lock keys
    • /, =, * Key when Caps Lock is enabled

    Portuguese Windows Keyboard:
    • Application Key, PrtScrn, Scroll Lock keys

    Italian Windows Keyboard:
    • Windows Key, Application Key, Left Arrow, End, F12 and PrtScrn, Scroll Lock keys

    Spanish Windows keyboard:
    • Application Key, PrtScrn, Scroll Lock keys

    Japanese Mac Keyboard:
    • _, F11, 英数, かな

    German Mac Keyboard:
    • ´,`,F11
    • 1,2,3,4,5,6,7,8,9,0,ß,´,+,#,;,:,_, when Caps Lock is enabled
    • All keys that are entered with Alt + in Mac keyboard
    • All keys that are entered with Right Option + Right Shift in Mac keyboard

    Portuguese Mac Keyboard:
    • §,±,F11
    • All keys that are entered with Alt + in Mac keyboard
    • All keys that are entered with Right Option + Right Shift in Mac keyboard

    Italian Mac Keyboard:
    • à, CMD, F11, F12
    • All keys that are entered with Alt + in Mac keyboard
    • All keys that are entered with Right Option + Right Shift in Mac keyboard

    Spanish Mac keyboard:
    • ´, ¨, F11
    • All keys that are entered with Alt + in Mac keyboard
    • All keys that are entered with Right Option + Right Shift in Mac keyboard

    Workaround: None.

Known Issues from Earlier Releases

To view a list of known issues applicable from earlier releases, click here.

General Issues

  • Attempts to configure single sign-on in vCloud Director fails when you are using vCenter Server 6.0 Update 2 and TLS 1.0 is disabled in vCenter
    To register lookup service for single sign-on in vCloud Director, Transport Layer Security (TLS) 1.0 must be enabled in vCenter Server 6.0 Update 2. If TLS 1.0 is disabled in vCenter, attempts to configure single sign-on fail with the following error.

    Error while attempting to contact the lookup service.
    - Received fatal alert: handshake_failure

    Workaround: Enable all TLS versions (1.0,1.1,1.2) in vCenter.

  • Attempts to upload or download an OVF or media file by using the vCloud Director Web client on a Google Chrome browser sometimes fail
    If you have both versions 6.0.0 and 5.6.0 of the Client Integration Plug-in installed, Google Chrome incorrectly attempts to use the Client Integration Plug-in 6.0.0 to upload and download OVFs and media files. This causes the upload or download operation to fail.

    Workaround: Use a Microsoft Internet Explorer or Mozilla Firefox browser to upload or download OVFs and media files.

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 or OVA file from a local datastore.

    1. Download the OVF or 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 or OVA file location on the local datastore, and click OK.
    5. Review the details of the uploaded OVF and click Next.
    6. Enter a name and optional description for the vApp.
    7. From the drop-down menu, select a virtual data center to store and run the vApp, 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 or OVA as a vApp template.

    1. Click Catalogs > My Organization's Catalogs.
    2. On the vApp Templates tab, click Upload.
    3. Enter the name and path of the OVF file to upload, and click Upload.
    4. Enter 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 Add vApp from Catalog.
    9. Select My organization's catalogs from the drop-down menu.
    10. Select the vApp template you created from the OVF or OVA file and click Next.
    11. Enter a name and optional description for the vApp.
    12. Select a runtime and storage lease and click Next.
    13. Select a virtual data center, 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 Plug-in version 5.6
    When you attempt to access vCloud Director using Mozilla Firefox or Google Chrome after you uninstall the Client Integration Plug-in 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 Plug-in version 5.6.

  • Google Chrome fails to detect the Client Integration Plug-in 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 Plug-in and prompts you to download the Client Integration Plug-in again.

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

Localization Issues

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

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

  • Attempts to modify the properties of a virtual machine on a storage cluster sometimes fail with a no usable datastore error message
    When you attempt to modify the properties of a virtual machine on a storage cluster, the operation fails with an error message similar to the following.

    com.vmware.ssdc.util.LMException: Could not find a suitable datastore in hub. There is no usable datastore.

    This issue occurs if the free space on the individual datastores in the cluster is less than the size of the virtual machine, and vCloud Director does not account for the fact that the virtual machine already resides on one or more of the datastores in the cluster.

API Issues

  • Configuration script offers an unsupported database as a valid choice
    When you are configuring network and database connections, the configuration script lists vPostgres as a supported database type. vPostgres is not supported for use with vCloud Director 8.0. Supported database types are Oracle and Microsoft SQL Server.

    Workaround: Select a supported database type during this configuration step. If you have already configured vCloud Director to use the unsupported vPostgres database type, you must uninstall vCloud Director and reinstall it to configure a supported database type.

  • Attempts to redeploy an Edge gateway in an SDRS cluster sometimes fail
    When you use vCloud Director to redeploy an Edge gateway in an SDRS cluster where the movement of virtual machines is fully automated, the operation sometimes fails or puts the Edge gateway into an inconsistent state.

  • Organization query provides an incorrect value for number of groups in an organization
    The response to an organization query, QueryResultOrgRecordType, provides an incorrect value for the numberOfGroups attribute. The value provided is actually the number of users in the organization. You cannot use the query service to obtain the number of groups in an organization.

  • Delete organization VDC behavior change in vCloud API 5.7
    For clients specifying vCloud API version 5.7 in requests, removal of an organization VDC has become an asynchronous operation. As a result, the response to the delete VDC request like this one:

    DELETE https://vcloud.example.com/api/admin/vdc/{id})

    is now:

    HTTP status 202 (Accepted)
    Content-Type: application/vnd.vmware.vcloud.task+xml

    Clients using vCloud API version 5.6 and earlier do not see any change in behavior of this request. The request is synchronous and HTTP status 204 (No Content) is returned after the VDC is removed.

Collapse List of Earlier Known Issues

Top of Page