vCloud Director 220.127.116.11 for Service Providers | 20 FEB 2020 | Build 15631706 (installed build 15631707)
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New
- System Requirements and Installation
- Previous Releases of vCloud Director 9.5.x for Service Providers
- Resolved Issues
- Known Issues
The vCloud Director 18.104.22.168 for Service Providers Express Patch Release provides bug fixes, updates the vCloud Director appliance base OS and the vCloud Director open-source components.
System Requirements and Installation
For information about system requirements, see vCloud Director 9.5 for Service Providers Release Notes.
To access the full set of product documentation, go to VMware vCloud Director for Service Providers Documentation.
Previous Releases of vCloud Director 9.5.x for Service Providers
See the vCloud Director 9.5.x Release notes for other Known Issues and Resolved Issues.
- Adding a new distributed firewall rule to vCloud Director or editing an existing rule fails
In the vCloud Director Service Provider Admin Portal, when you add a new distributed firewall rule or when you edit an existing firewall rule, the operation fails with an error message:
Precondition failed. Please update the current configuration with latest generation Number.
- The vCloud Director Web console shows incorrect value of the network CIDR in an organization VDC template
In the vCloud Director Web console, when you edit an existing organization VDC template the displayed value of the network CIDR in the Edit Organization VDC Template wizard is incorrect and you cannot update the template.
- In the vCloud Director Tenant Portal, the Networks page does not display all of the existing organization VDC networks
If the network is in a Provider VDC that is backed by multiple clusters, the Networks page under Datacenters does not display the full list of available organization VDC networks.
- Excessive CPU usage slows down the performance of the vCloud Director appliance
In the vCloud Director Tenant Portal, when you open a VM console, you observe a degradation in the performance of the vCloud Director due to excessive CPU usage.
- You cannot assign a custom IP address to a virtual server
When you try to add a virtual server to an edge gateway, you can select only the primary IPv6 from the pre-configured suballocated pool with IPv6 addresses.
- With AES-GCM as encryption algorithm for IPsec VPN, opening the properties of an edge gateway fails
If during configuration of the IPsec VPN sites you selected
AES-GCMas the encryption algorithm, viewing the properties of an edge gateway with enabled the IPsec VPN service fails with an error message.
- In the vCloud Director Tenant Portal, displaying the list with organization VDC networks times out
In the vCloud Director Tenant Portal, when you navigate to Networking > Networks, displaying the list with organization VDC networks might fail with a timeout.
- Editing the properties of an edge gateway fails with an error message
Editing the properties of an edge gateway, which IPsec VPN site is configured with subnet_prefix_length of 32 or higher, fails with an
- When you enable the Syn Flood protection through the NSX API, any firewall change in vCloud Director disables the SynFlood protection
After enabling the SynFlood protection by executing requests to the NSX API, firewall changes on an edge gateway revert the
- After removing the default static route IP address for an edge gateway, all of its associated static routes are automatically deleted
In the vCloud Director Tenant Portal and in the vCloud Director Service Provider Admin Portal, when you remove the default static route IP address for an edge gateway, all of the associated static routes are deleted from the Static Routes page.
- NSX Manager experiences a slowdown in performance
When you perform operations on edge gateways, you observe a degradation in the performance of the NSX Manager due to excessive CPU and memory usage.
- Synchronization between vCenter Server and vCloud Director might take very long to complete
In the vCloud Director Web Console, when you try to reconnect a vCenter Server instance to vCloud Director, the reconnect operation might take very long time to complete.
- Configuring virtual server for load balancing fails
In the vCloud Director Web Console, when you add a virtual server IP as an edge gateway for load balancing, you get an error message.
Virtual server IP should be part of the subnet of network.
- When you use API, you can create a snapshot of a vApp or VM located outside your current organization VDC
If you have a local organization administrator credentials, by using the API you can create snapshots of vApps and VMs located in other organization VDCs.
- Powering on or off a VM fails with an error message
Upon a VM power on or off operation, vCloud Director invokes vCenter Server API to execute the operation. If the vCenter Server proxy is processing simultaneously a large number vCenter Server datastore events, the processing time for VM power operations increases. If the vCenter Server proxy does not receive the task for a certain period, the task fails with an
Unable to find objecterror.
- Updating the NSX edge gateway services fails with an error message
In the vCloud Director Tenant Portal, attempting to edit the NSX services on an edge gateway fails with an
403 Forbiddenerror message.
- Email for an expired vApp is sent to all members of the organization instead of sending it only to the organization administrator
When a vApp storage lease expires, an email notification is sent not only to the organization administrator, but also to all members of the same vCloud Director organization, irrespective of their assigned user role.
- vCloud Director organization administrators receive bounce email from firstname.lastname@example.org
When vCloud Director sends alert email notifications to the default user account
email@example.com, the organization administrators receive a bounce email from
- You cannot power on a VM after adding a subsequent hard disk
If you add a subsequent hard disk to a VM that is in an elastic VDC backed by multiple clusters, powering on the VM fails with an error message.
The operation could not be performed because the argument is invalid. A specified parameter was not correct
- Updating the properties of an NSX edge gateway causes a redeployment of the same edge gateway
If you configure an NSX edge gateway as Large, when you update its properties, the vApp placement engine redeploys the same NSX edge gateway.
- Using the vCloud Director REST API to run a GET query might not return the full list with edge gateways
For an organization VDC configured with 1000 or more edge gateways, an API
GET /network/edgesquery does not return the full list of edge gateways in an organization VDC.
- The status of a load balancer pool server is displayed as red
In the vCloud Director Web Console, the status of a load balancer pool server is displayed as red (Down), even if the pool server operational status is green (Up) in the vSphere Web Client.
- You cannot move a vApp from your current organization VDC to another organization VDC
In the vCloud Director Tenant Portal, when you attempt to move a vApp from your current organization VDC to another organization VDC, in the Select destination vApp wizard you cannot select a vApp outside your current organization VDC.
Workaround: To move a vApp from your current organization VDC to another organization VDC, use the vCloud Director Web console.
- You cannot delete organization VDC networks from the vCloud Director Tenant Portal
When you have an organization VDC network assigned to a vApp that is connected to a virtual machine, an attempt to delete the organization VDC network from the vCloud Director Tenant Portal fails with the following error message.
Entity to-be-deleted cannot be deleted, because it is in use.
Workaround: To delete an organization VDC network follow the steps.
- Log in to the vCloud Director Web console as an administrator.
- Navigate to System > Organizations and select your organization name.
A window with all vApps, associated to your organization opens.
- Select the organization VDC vApp and navigate to the Networking tab.
- Right-click the organization VDC network you want to delete and select Delete.
- To complete the deletion, click Apply.
- Newly added network interface to a virtual machine is not connected
In the vCloud Director Tenant Portal, when you add a new network interface to a virtual machine, the Connected check box for the NIC is not connected by default.
Workaround: To configure the new NIC to have network connection, you must manually select the Connected check box.
- Existing organization VDC networks are not showing operational status in the vCloud Director Tenant Portal
In the vCloud Director Tenant Portal, when you navigate to Networking > Networks, some of the organization VDC networks do not show an operational status.
Workaround: Update a property of the organization VDC network by following the steps in the Edit an Organization Virtual Data Center Network procedure.