vCloud Director 9.0.0.2 for Service Providers Release Notes

|

vCloud Director 9.0.0.2 for Service Providers | 16 JAN 2018 | Build 7553273 (installer build 7554058)

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

System Requirements and Installation

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

Documentation

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

Known Issues

See the vCloud Director 9.0 for Service Providers Release Notes for Known Issues.

Resolved Issues

  • The Allocation tab under Organization VDC Properties for a particular Organization VDC network shows incorrect values in both the vCloud Director user interface and in response to a GET /ext/admin/vdc/{OrgVDC ID} request 

    After you update the allocated resources for an Organization VDC network, the Allocation tab under Organization VDC Properties still shows the values that you originally set for that network. When you send a GET request to the /ext/admin/vdc/{OrgVDC ID} API, the ComputeCapacity element of the XML response message also shows the values that you originally set.

  • Deleting a Provider VDC can corrupt VXLAN network pools that are in use

    After you delete a Provider VDC, its associated VXLAN network pool becomes unusable by organization VDCs backed by other Provider VDCs.

  • The Redeploy an Edge Gateway from vCloud Director task succeeds instantly but the Edge does not actually redeploy in NSX

    When you attempt to redeploy an Edge Gateway from vCloud Director, the API initiates a task in vCloud Director and in vCenter Server but does not send a redeploy request to the NSX server. As a consequence, the Edge Gateway does not redeploy.

  • Registration of an NSX Server fails when you supply the credentials of an SSO user

    vCloud Director SSO users are not authorized to access an NSX endpoint required for registration, so registration fails.

  • Changes on Edge Gateway Services are not synchronized between vCloud Director and NSX

    When you modify one of the Edge Gateway Services, for example by creating a Static Route, the change is saved on the vCloud Director side but cannot be saved on the NSX server.

  • After an upgrade to vCloud Director 9.0, creating a Provider VDC might fail

    After upgrading vCloud Director to 9.0, an attempt to create a Provider VDC by creating a new VXLAN network pool or by adding an existing one might fail with a NullPointerException error.

  • Creating or updating a firewall rule for an Advanced Gateway Portal with enabling the Show only user-defined rules toggle causes the action of the default firewall rule to change.

    When you create a new firewall rule or update an existing rule for an Advanced Gateway Portal, if you enable the Show only user-defined rules toggle, the action of the default firewall rule changes incorrectly to match the last modified rule.

  • Deleting an external network that uses a distributed virtual port group with a Private VLAN does not work

    When you try to delete an external network that is linked to a private VLAN associated with a distributed virtual port group (dvPortgroup), the deletion fails with an InternalError: Only single VLAN or trunk VLAN is supported error message.

  • Catalog synchronization fails at subscriber side with an Unable to retrieve OVF descriptor error message

    When multiple vCloud Director cells initiate a transfer for a catalog item and a cell different from the one that created the transfer session contacts the subscriber catalog, the transfer fails. The reason for the failure is that the cell that did not initiate the transfer sends an empty user name and password when connecting to the subscriber library.

  • You cannot add a DNAT rule configuring an original or a translated port or port range through the tenant portal

    When you attempt to add a DNAT rule from the Edge Gateway screen in the tenant portal, you cannot enter either a port or a port range in the Original Port and the Translated Port text boxes.

  • When the API authorization session expires, the vCloud Director API returns a 403 Forbidden HTTP response

    When the x-vcloud-authorizaiton header is invalid or has expired, the vCloud Director API returns a 403 Forbidden instead of a 401 Unauthorized HTTP status code.

  • Setting a dynamic membership for a security group through the vCloud Director user interface does not work as expected

    When you create a new Orcanization VDC and enable a distributed firewall, vCloud Director creates a security group but does not set a dynamic membership for that group. As a result, virtual machines are not automatically associated with the firewall rules configured for the Organization VDC.

  • Guest OS customization for a Windows Server 2016 guest operating system does not work with the Change SID option enabled

    When you install a Windows Server 2016 from a vCloud Director template and select Enable guest customization and Change SID from the virtual machine properties, the guest customization completes but does not apply the custom settings to the operating system.

  • Creating a SNAT or a DNAT network rule by using a public IP address that is not associated to a particular network interface fails

    When you try to create a SNAT or a DNAT network rule for either an internal or an external interface in vCloud Director, if the public IP address is not added to a particular network interface, you receive a the following error message:

    A NAT rule has an invalid vnic value 1. The value should be a vnic index number.

  • Deploying a virtual machine from a template in vCloud Director 9.0 clones the value of the uuid.bios parameter from the template even if you explicitly set the backend.cloneBiosUuidOnVmCopy property to 0

    In vCloud Director 9.0, when you deploy a virtual machine from an existing vApp template, the new machine receives the same BIOS UUID as the template even if you changed the configuration of the vCloud Director instance to not copy the uuid.bios parameter from the template. As a result, multiple virtual machines in vCenter Server have the same BIOS UUID.

  • Configuring a static route fails if you set the gateway of an external network as a next hop IP address

    When you configure a static route for an organization network, if you enter the address of an existing default gateway in the Next Hop IP text box, saving the static route configuration fails with the following error message:

    Static route's next hop router "IP_address" cannot be same as gateway.

  • Deleting a role template does not remove the associated role instances

    During the upgrade to vCloud Director 8.20, the existing roles are converted to role templates. For any existing role, the original role ID becomes the default role ID of the template. The template that is created from the role receives a new ID that is different from the original role ID. As a result, the deletion of a role template does not remove the role instances that are associated to this template.  

  • Creating an organization by using Guided Tasks in vCloud Director fails if you add users as part of the wizard setup

    When you use Create another organization from the Allocate additional organization resources section under Guided Tasks in vCloud Director, if you add local users as part of the setup, you cannot complete the configuration. The wizard fails with an Invalid role ID specified error message.

  • You cannot power on a vApp that uses a routed organization network connected to an external direct organization vDC network with more than one subnet

    When a vApp is configured to use a routed organization network that is connected to an external direct organization vDC network with multiple subnets, starting the vApp fails with an Unable to deploy network, query did not return a unique result: 2 error message.