vCloud Director 10.0.0.3 for Service Providers | 17 SEP 2020 | Build 16869394 (installed build 16869149)

Check for additions and updates to these release notes.

What's in this Document

What's New

The vCloud Director 10.0.0.3 Release provides bug fixes, updates the vCloud Director appliance base OS and the vCloud Director open-source components. This release introduces additional support of guest customization on virtual machines running Ubuntu 20.04 or Photon OS.

Caveats and Limitations

You cannot enable guest customization on a virtual machine running one of the following operating systems:

  • Windows Server 2003
  • Windows Server 2000
  • Windows XP
  • Red Hat Enterprise Linux 4.x
  • Ubuntu 13.10
  • Ubuntu 13.04
  • Ubuntu 10.04

System Requirements and Installation

For more information about system requirements and installation instructions, see vCloud Director 10.0 for Service Providers Release Notes.

Documentation

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

Previous Releases of vCloud Director 10.0.x for Service Providers

vCloud Director 10.0.0.2 for Service Providers Release Notes

vCloud Director 10.0.0.1 for Service Providers Release Notes

vCloud Director 10.0 for Service Providers Release Notes

Resolved Issues

  • Powering on a VM in a newly deployed vApp fails with an error message

    During a deployment of a new vApp, if you configure a direct organization VDC network with both IPv4 and IPv6, powering on the newly deployed IPv6 VM fails with an error message.
    Following errors occurred while updating network connections: Invalid network parameter: Specified address is not in the subnet range.

  • You can view and delete an Anti-Affinity rule located outside your current organization VDC

    If you add more than one vCenter Server instances in vCloud Director, in the vCloud Director tenant portal you can view and delete an anti-affinity rule located in other organization VDC.

  • The New Security Group wizard becomes unresponsive while adding a virtual machine as a member of a security group

    In the New Security Group wizard, if you try to add a VM object as a new member of a security group by clicking the import icon instead of selecting the object from the left panel, and move it to the right panel by clicking the right arrow, the wizard becomes unresponsive.

  • When using the vCloud Director API, reverting a vApp with multiple VMs to a snapshot fails

    If you have multiple VMs in a vApp, when you try to revert the vApp to a snapshot by using an API, the operation fails with a HibernateException error message.

     

  • You cannot log out from VMware Cloud Director by initiating a single logout from an external application

    If you configure VMware Cloud Director with a SAML identity provider(IDP) and the third-party IDP supports SAML-based Single Logout protocol, logging out of the third-party IDP does not terminate the VMware Cloud Director session.

  • Copying a virtual machine fails with an error message

    When you try to copy a VM, the operation fails with an error message.
    VimInvalidStateException: The operation could not be performed because the object is in an invalid state

  • You cannot select an object when executing a vRealize Orchestrator workflow from the VMware Cloud Director service library

    If you initiate a vRealize Orchestrator workflow imported as a VMware Cloud Director service, the option to select an object from the service wizard is disabled and you are unable to proceed with the service execution.

  • Configuring the interface of an organization VDC network to subinterface fails

    If an organization VDC network is associated with an edge cluster, configuring the network interface to Subinterface fails with an error message.
    VXLAN Network Pool does not have correct vds contexts. Cannot add subinterfaces

  • Migration of a virtual machine between resource pools fails

    In a VM configured with multiple hard disks, if you assign different storage policies to the virtual disks, migrating the VM from one resource pool to another fails with an error message. 
    The operation failed because no suitable resource was found. Could not find a suitable datastore in hub.

  • Adding an external network by using the HTML5 UI deletes the existing external network information from the edge gateway

    On the External Networks page of the Edit Edge Gateway wizard, if you select a new external network from a page with a lower index number than the page of the initially configured external network, the existing external network is deleted from the edge gateway.

  • In a flex organization VDC, the values of the CPU, memory, and storage hardware resources are zero

    If you configure an organization VDC to use the flex allocation model, the values of the used hardware resources, such as CPU, memory, and storage on the Virtual Datacenters dashboard screen of the vCloud Director tenant portal are zero.

Known Issues

  • Quiescing or pausing the primary cell in a multi-cell environment does not restart the periodical tasks on the secondary cell

    In a multi-cell environment, when you quiesce or pause the primary cell, the periodical tasks that are running in the background of the primary cell are not started from the secondary cell.

    Workaround: Restart the vCloud Director services on the cell.

  • In the vCloud Director Service Provider Admin Portal, deletion of an organization Virtual Data Center fails with a Cannot delete organization VDC network error message

    In the vCloud Director Service Provider Admin Portal, you add an edge gateway to your organization virtual data center and enable the gateway to provide vCloud Director Distributed Routing.

    When you try to delete the organization virtual data center recursively, the deletion fails with a Cannot delete organization VDC network error message.

    Workaround: To delete the organization VDC, follow the steps.

    1. By using API, delete the organization VDC networks and the edge gateways associated with the organization VDC that you want to delete.
    2. By using API, delete the organization VDC.
  • If you disable the provider access to the legacy API login endpoint, all API integrations that rely on the system administrator login stop working, including vCloud Usage Meter and vCloud Availability for vCloud Director

    Starting with vCloud Director 10.0, you can use separate vCloud Director OpenAPI login endpoints for service provider and tenant access to vCloud Director. If the service provider access to the legacy /api/sessions  endpoint is disabled, it causes products that integrate with vCloud Director, like vCloud Usage Meter and vCloud Availability for vCloud Director, to stop working. These products will require a patch to continue to operate.

    The issue affects only system administrators. The tenant login is not affected.

    Workaround: Re-enable the service provider access to the legacy /api/sessions  endpoint by using the cell management tool.

  • When you change the  reservation guarantee values of a VDC, the existing VMs are not updated accordingly even after a reboot

    If you have a flex organization VDC with the system default policy and powered-on virtual machines on that VDC are with the default sizing policy, when you increase the resource guarantee value of the VDC, the resource reservation for the existing VMs is not updated and they are also not marked as non-compliant. The issue occurs also when you convert a legacy VDC allocation model to a flex allocation model and the existing VMs become non-compliant with the new default policy of the flex organization VDC after the conversion.

    Workaround:

    1. To find the VM identifier, in the vCloud Director Tenant Portal, navigate to the Details page of the VM. The URL shows the identifier
      https://Cloud_Director_IP_address_or_host_name/tenant/.../vm-Identifier/general
    2. To display the non-compliant VMs in the vCloud Director UI, perform an explicit compliance check against the VMs by using the VMware Cloud Director API.
      POST: https://VCD_IP_Address/api/vApp/vm-Identifier/action/checkComputePolicyCompliance
    3. To reapply the policy and reconfigure the resource reservations, in the vCloud Director Tenant Portal, click Make VM Compliant for a non-compliant VM.
  • vCloud Director displays incorrect information about running and total VMs and CPU and memory stats in dedicated vCenter Server instances

    If a dedicated vCenter Server is version 6.0 U3i or earlier, 6.5U2 or earlier, or 6.7U1 or earlier, vCloud Director displays incorrect information about running VMs, total VMs, and CPU and memory statistical information in the vCenter Server instance. The dedicated vCenter Server tile in the Tenant Portal and the dedicated vCenter Server information in the Service Provider Admin Portal display zero for both running and total VMs, even when there are virtual machines in the vSphere environment.

    Workaround: Upgrade the vCenter Server instance to version 6.0 U3j, 6.5U3, 6.7U2 or later.

  • If the current primary cell is healthy, you cannot promote a standby cell to primary by using the appliance management user interface 

    If the primary node is healthy, the Promote button in the appliance management UI does not work.

    Workaround: Switch the roles of the primary and a standby by using the Replication Manager Tool suite. For more information, see Switch the Roles of the Primary and a Standby Cell in a Database High Availability Cluster.

  • Updating a VM sizing policy fails with a memory allocation error

    If you convert an allocation-pool VDC to a flex organization VDC, vCloud Director keeps the maximum policy information from the allocation-pool VDC before the conversion. CPU or memory reservation guarantees higher than the reservations defined in the allocation-pool VDC fail with a Virtual machine reservation or limit or shares settings are invalid error.

    Workaround: Log in as a system administrator and set a new maximum policy with the new resource reservation guarantees.

  • Used NICs count in edge gateways grid is incorrect for NSX-T Edge Gateways

    For NSX-T organization VDC edge gateways, the number of used NICs displayed in the Edge Gateways page of the vCloud Director Service Provider Admin Portal is incorrect.The issue does not affect the functionality itself.

    Workaround: None.

  • Cannot configure the system to use a SAML identity provider by using the vCloud Director Service Provider Admin Portal

    After you configure your system to use a SAML identity provider by using the vCloud Director Service Provider Admin Portal, you cannot log in again to the vCloud Director Service Provider Admin Portal.

    Workaround: Configure your system to use a SAML identity provider by using the vCloud Director Web Console.

  • In the tenant H5 UI, not all organization VDC networks are displayed when adding an organization VDC network to a vApp

    In the tenant H5 UI, when you try to select an organization VDC network to add to a vApp, the H5 UI does not display the full network list. This is observed only with shared organization VDC networks when a multi-clustered backed PVDC is used.

    Workaround: Use vCloud Director Web console (Flex UI).

  • Cannot access an SDDC proxy if vCloud Director uses legacy self signed certificates

    After the upgrade to vCloud Director 9.7, connecting to an SDDC proxy might fail with the error message: verify error:num=20:unable to get local issuer certificate. This issue happens if you generated the self signed certificates by using the cell management tool in vCloud Director 9.5 or earlier.

    Workaround: After the upgrade to vCloud Director 9.7, regenerate and update the self signed certificates.

  • After the upgrade to vCloud Director 9.7 (vCloud API v.32.0), custom links that you added by using branding OpenAPI calls are removed

    In vCloud API v.32.0, type UiBrandingLink that is used for custom links is replaced by type UiBrandingMenuItem. These types have different elements. This change is backward incompatible. As a result, API calls from versions 31.0 or earlier that attempt to process or set customLinks within a UiBranding object fail.

    Workaround: Update your API calls to the new data type.

  • Changing the compute policy of a powered on VM might fail

    When trying to change the compute policy of a powered on VM, if the new compute policy is associated with a provider VDC compute policy that has VM Groups or Logical VM Groups, an error occurs. The error message contains: Underlying system error: com.vmware.vim.binding.vim.fault.VmHostAffinityRuleViolation.

    Workaround: Power off the VM, and retry the operation.

  • When using the vCloud Director Service Provider Admin Portal with Firefox, you cannot load the tenant networking screens

    If you are using the vCloud Director Service Provider Admin Portal with Firefox, the tenant networking screens, for example, the Manage Firewall screen for an organization virtual data center, might fail to load. This issue happens if your Firefox browser is configured to block Third-Party cookies.

    Workaround: Configure your Firefox browser to allow third-party cookies.

  • vCloud Director 9.7 supports only a list of input parameters of vRealize Orchestrator workflows

    vCloud Director 9.7 supports the following input parameters of vRealize Orchestrator workflows:

    • boolean
    • sdkObject
    • secureString
    • number
    • mimeAttachment
    • properties
    • date
    • composite
    • regex
    • encryptedString
    • array

    Workaround: None

  • A fast-provisioned virtual machine created on a VMware vSphere Storage APIs Array Integration (VAAI) enabled NFS array, or vSphere Virtual Volumes (VVols) cannot be consolidated

    In-place consolidation of a fast provisioned virtual machine is not supported when a native snapshot is used. Native snapshots are always used by VAAI-enabled datastores, as well as by VVols. When a fast-provisioned virtual machine is deployed to one of these storage containers, that virtual machine cannot be consolidated .

    Workaround: Do not enable fast provisioning for an organization VDC that uses VAAI-enabled NFS or VVols. To consolidate a virtual machine with a snapshot on a VAAI or a VVol datastore, relocate the virtual machine to a different storage container.

  • Org VDC network status is blank

    In the H5 tenant portal, the status of some old operational Org VDC networks appears as blank.

    Workaround: Change a property of the Org VDC network (e.g. description) and save it.

  • Organization VDC network cannot be deleted from the Tenant portal

    You have added a VDC network to a vApp and you have connected the same vApp to a virtual machine.
    When you try to delete the organization VDC network in the tenant portal, you receive an error message and you cannot proceed with the deletion.
    This network is in use.

    Workaround: To delete the organization VDC network follow the steps.

    1. In vCloud Director Web console, navigate to System > Organizations, and select your organization name.
      A window with all vApps, associated to your organization opens.
    2. Select the organization VDC vApp and navigate to the Networking tab.
    3. Right-click the organization VDC network you want to delete and select Delete.
    4. To delete the organization VDC network, click Apply.
  • When creating an Anti-Affinity Rule in the vCloud Director tenant portal, the UI displays empty virtual machine list

    When you try to create an Anti-Affinity rule in the vCloud Director tenant portal, you cannot select a virtual machine to add to the rule because the virtual machine selection list is empty.

    Workaround: To create an Anti-Affinity Rule, use the vCloud Director Web console.

  • Newly created virtual machines are deployed on the organization VDC default storage policy

    In the vCloud Director Tenant Portal, when you create a new standalone virtual machine, the option to specify the storage policy is missing. As a result the created virtual machine is deployed with the default storage policy of the organization VDC.

    Workaround: After you create the virtual machine, go to the resulted virtual machine properties and change the storage policy.

check-circle-line exclamation-circle-line close-line
Scroll to top icon