vCloud Director 8.0 for Service Providers Release Notes
vCloud Director 8.0 for Service Providers | 24 SEP 2015 | Build 3017494
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
- vSphere 6.0 support: vCloud Director for Service Providers 8.0 adds support for vSphere 6.0 in backward
- NSX support: vCloud Director for Service Providers 8.0 adds support for NSX 6.1.4 in backward
compatibility mode. This means that tenants' consumption capability is unchanged and remains at the vCloud Networking and
Security feature level of vCloud Director 5.6.
- Organization virtual data center templates: Allows system administrators to create organization virtual data center templates,
including resource delegation, that organization users can deploy to create new organization virtual data centers.
- vApp enhancements: Enhancements to vApp functionality, including the ability to reconfigure virtual machines within a vApp, and
network connectivity and virtual machine capability during vApp instantiation.
- OAuth support for identity sources: Support added for OAuth2 tokens.
- Tenant throttling: : Prevents a single tenant from consuming all of the resources for a single instance of vCloud Director and
ensures fairness of execution and scheduling among tenants.
System Requirements and Installation
For information about system requirements and installation instructions, see the
VMware vCloud Director Installation and Upgrade Guide.
vCloud Director 8.0 for Service Providers does not support HW11.
To access the full set of vCloud Director 8.0 for Service Providers documentation, go to the
vCloud Director for Service Providers Documentation page.
The following issues are known to occur in this release of vCloud Director.
Attempts to log in to vCloud Director from a Windows operating system configured to use Security Support
Provider Interface (SSPI) fail
When you attempt to log in to vCloud Director from a Windows operating system configured to use SSPI, the operation fails
with the following error message.
Unable to perform this action. Contact your cloud Administrator.
Workaround: Disable SSPI on Windows.
Repeated system alert emails stating runtime lease is going to expire
When a vApp's runtime lease has expired and the storage lease is set to expire within the next five days, vCloud Director sometimes does not properly
suspend the vApp, which leaves the vApp's virtual machines in a partially suspended state. This causes vCloud Director to send system alert emails
stating the vApp's runtime lease is going to expire.
Workaround: Resolve this issue in one of three ways.
- Suspend or stop the virtual machines in the vApp.
- Reset the runtime or storage lease.
- Change the frequency of lease expiry emails in the database configuration.
Objects sometimes display a status of Pending after upgrading to vCloud Director for Service Providers 8.0
When you upgrade to vCloud Director for Service Providers 8.0 while activities are in progress, vCloud Director sometimes displays objects with a status
of Pending. This is a cosmetic error and does not impact functionality.
Workaround: Perform any operation on the object to clear the incorrect Pending status.
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
Installation and Upgrade Issues
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 8.0, the host agent upgrade fails.
Workaround: Unprepare the host to remove the host agent, then prepare the host agent again.
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.
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.
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.
- In the vCloud Director Web client, click the Manage & Monitor tab and click Hosts in the left pane.
- Right-click the host name and select Prepare Host.
- Type a user name and password and click OK.
Virtual Machine and vApp Issues
vCloud Director sometimes displays the status of a new virtual machine as Pending
When you create a virtual machine, vCloud Director sometimes displays a status of Pending for the virtual machine. When you
click the Pending link, the following error message appears.
Error During Validation
The virtual machine continues to function normally, and you can safely ignore this error.
- 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.
- In the vCloud Director Web client, click the Administration tab and click General in the left pane.
- Select Allow allocation pools to be elastic and click Apply.
Missing guest operating system error during vApp creation
When you attempt to create a vApp on a provider virtual data center configured with hardware compatibility set to HWV 11, the operation fails with a
missing guest operating system error. This occurs because vSphere 6.0 supports HWV 11 while vCloud Director 8.0 for Service Providers does not.
Workaround: Create a new provider virtual data center with hardware compatibility set to HWV 10.
vCloud Director web client page sometimes refreshes after you delete a vApp
When you delete a vApp, the vCloud Director web client page sometimes refreshes, but the deletion is successful.
Attempts to create a virtual machine from a catalog sometimes fail
When you attempt to create a virtual machine from a catalog associated with vCenter Server version 6.0, the operation fails
with the following error message.
Workaround: Edit the virtual machine in ESX Server, and retry the operation.
- Use ssh to log in to the ESX server where the affected vApp or vApp template resides.
- Run the command
vim-cmd vmsvc/getallvms to list down all the virtual machines running on the ESX server.
You can use grep to filter the results if you have longer list.
- Make a note of the
Vmid in the first column for the affected virtual machine or template.
- Run the command
vim-cmd vmsvc/reload Vmid.
- Retry the create virtual machine operation.
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:
HTTP status 202 (Accepted)
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.
The following cell-management-tool commands are not supported for customer use.
delete-vdc-template - Deletes a specified VDC Template or all VDC templates
instantiate-vdc-template - Instantiates a VDC template for a specified Org
list-vdc-templates - Lists a single VDC Template or all VDC Templates in a server group
make-vdc-template - Creates a new VDC Template or updates an existing template
manage-vdc-template-access - Manage access settings for a VDC Template