vCloud Director 8.0.1 for Service Providers Release Notes

Updated on: 16 MAR 2016

vCloud Director 8.0.1 for Service Providers | 15 MAR 2016 | Build 3635340

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

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

  • Increased vSphere support: vCloud Director 8.0.1 for Service Providers supports vSphere versions 6.0U2, 6.0U1, and 5.5U3. vCloud Director 8.0.1 for Service Providers adds support for vSphere 6.u1 and 60u2 in backward compatibility mode.
  • Increased NSX support: vCloud Director 8.0.1 for Service Providers supports NSX versions 6.2.2, 6.2.1, 6.1.6, and 6.1.5.
  • Increased vCloud Networking and Security support: vCloud Director 8.0.1 for SErvice Providers supports vCloud Networking and Security versions 5.5.4.2 and 5.5.4.1.
  • Increased platform OS support: vCloud Director 8.0.1 for Service Providers adds support for the following platform operating systems.
    • Cent OS 7.0 (64 bit)
    • Cent OS 6.7 (64 bit)
    • Cent OS 6.6 (64 bit)
    • Red Hat Enterprise Linux 7.0 (64 bit)
    • Red Hat Enterprise Linux 6.7 (64 bit)
    • Red Hat Enterprise Linux 6.6 (64-bit)
  • Guest customization for Windows 10: vCloud Director 8.0.1 for Service Providers adds guest customization support for Windows 10.
  • JRE version update: vCloud Director 8.0.1 for Service Providers uses JRE version 1.7.0_95.

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.

vCloud Director 8.0.1 for Service Providers uses TLS version 1.2 by default, but will fall back to TLS version 1.0 when the server supports a lower protocol.

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

  • vCloud Director Web client incorrectly displays a pending status for some objects
    When you select an object such as a virtual data center, network, or Edge gateway in the left pane of the vCloud Director Web client, vCloud Director sometimes incorrectly displays a status of Pending. This occurs when no actions have been performed on the object within the time limit set to clean up audit event data. This issue is resolved in vCloud Director 8.0.1.

  • vCloud Director incorrectly sends multiple notification emails for the same networking issue
    When a networking issue triggers a notification in vCloud Director, vCloud Director incorrectly sends a notification email for each cell affected by the issue instead of a single email for the event. This issue is resolved in vCloud Director 8.0.1.

  • Attempts to enable elastic allocation pool virtual data centers fail
    When you select the Make Allocation Pool Org VDCs elastic checkbox in the System settings of the vCloud Director Web client and click Apply, vCloud Director does not check the checkbox. This issue is resolved in vCloud Director 8.0.1.

Networking Issues

  • vCloud Director Web client becomes unresponsive when you attempt to view an Edge gateway's properties
    When you attempt to view an Edge gateway's properties in the vCloud Director Web client, the Web client becomes slow or unresponsive. vCloud Director 8.0.1 resolves this issue by displaying Edge gateway external networks across multiple pages, with ten external networks displayed on each page.

  • Attempts to add a second external network to an Edge gateway fail
    When you attempt to add a second external network to an Edge gateway, the operation fails with the following error message.

    Violation of UNIQUE KEY constraint 'uq_plac_subj_ite_su_id_i_u_i_t'. Cannot insert duplicate key in object 'dbo.placement_subject_item'.

    This issue is resolved in vCloud Director 8.0.1.

  • Attempts to create an Edge gateway on a system that includes a network isolation-backed network pool fail
    When you attempt to create an Edge gateway on a system that includes a network isolation-backed network pool, the operation fails with the following error message.

    No host is compatible with the virtual machine.

    This issue is resolved in vCloud Director 8.0.1.

Virtual Machine and vApp Issues

  • New Attempts to change the storage policy of a virtual machine on a storage cluster sometimes fail
    When you attempt to change the storage policy of a virtual machine on storage cluster sometimes fail with an error message similar to the following.

    Could not execute JDBC batch update; SQL [insert into placement_subject_item (existing_item, item_type, item_uri, subject_id, target_uri, id) values (?, ?, ?, ?, ?, ?)]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
    - Could not execute JDBC batch update

    This issue is resolved in vCloud Director 8.0.1.

  • Audit event does not reflect changes made to CPU, memory, or storage during vApp instantiation
    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 8.0.1.

  • vCloud Director does not migrate virtual machine after switching to a storage policy with SDRS disabled
    After you modify a virtual machine to use a storage policy with a datastore that has SDRS disabled, vCloud Director fails to migrate the virtual machine. This issue is resolved in vCloud Director 8.0.1.

  • Attempts to add a vApp from a catalog using Add to My Cloud fails with a null storage policy error
    When you attempt to add a vApp from a catalog by clicking Add to My Cloud in the vCloud Director Web client, the vCloud Director Web client displays an empty Storage policy drop-down menu and the operation fails with an error message similar to the following.

    Cannot find the VDC storage policy "[null]".

    This issue is resolved in vCloud Director 8.0.1.

  • Attempts to create a new virtual machine, add or grow a virtual machine disk, or change the storage policy of a virtual machine or virtual machine disk on a storage cluster sometimes fail
    Some combinations of SDRS and fast provisioning interfere with creating, moving, and growing virtual machine disks on storage clusters. When you attempt to create a new virtual machine, add or grow a virtual machine disk, or change the storage policy of a virtual machine or virtual machine disk with SDRS enabled and fast provisioning disabled or both SDRS and fast provisioning disabled, the operation fails with a datastore not found error message. When you attempt any of these operations with both SDRS and fast provisioning enabled, the operation fails with an invalid parameter error message. This issue is resolved in vCloud Director 8.0.1.

API Issues

  • vCloud API incorrectly returns a virtual machine snapshot size of 0
    When you use the vCloud API call SnapshotSection, the vCloud API incorrectly returns a snapshot size of 0. This issue is resolved in vCloud Director 8.0.1.

  • The vCloud API sometimes does not return DateCreated attributes when querying a virtual machine
    When you use the vCloud query service to query a virtual machine, the vCloud API does not return the DateCreated attribute. This issue is resolved in vCloud Director 8.0.1.

Known Issues

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

General Issues

  • Attempts to configure single sign-on in vCloud Director fails when you are using vCenter 6.0U2 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 6.0U2. 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 (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 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 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.

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 occurs when 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 VCD 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 will see no change in behavior of this request. The request will be synchronous and HTTP status 204 (No Content) will be returned after the VDC is removed.