vCloud Director 126.96.36.199 for Service Providers | 12 NOV 2020 | Build 17135839 (installed build 17135848)
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New
- Caveats and Limitations
- System Requirements and Installation
- Previous Releases of vCloud Director 9.7.x for Service Providers
- Resolved Issues
- Known Issues
The vCloud Director 188.8.131.52 for Service Providers Patch 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 9.7 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.7.x for Service Providers
- NEW When using the HTML5 UI, you cannot share a catalog with specific users and groups
If you use the HTML5 UI to share a catalog with specific users and groups, the Users and groups with access list appears as blank and you cannot select the users or groups to whom you want to grant catalog access.
- Creating a vApp from a vApp template on a vCenter Server instance with enabled Storage DRS fails
If you enable Storage DRS on a vCenter Server instance that is attached to vCloud Director, creating a vApp from a vApp template on the same vCenter Server instance fails with an error message.
java.lang.ClassCastException: com.vmware.vim.binding.impl.vim.storageDrs.StorageMigrationActionImpl cannot be cast to com.vmware.vim.binding.vim.storageDrs.StoragePlacementAction
- 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.
- 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.
- 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
- The global tenant role vApp Author can upload and create templates and media without having the necessary right for these operations
The global tenant role vApp Author by default has the
Add a vApp from My Cloudright. Because this right and the
Template/Media: Create/Uploadright share a single operation, VMware Cloud Director incorrectly grants also the
Template/Media: Create/Uploadright to the vApp Author role.
The issue is fixed. If you want the vApp Author role to continue to have the
Template/Media: Create/Uploadright, a service provider can add the right to the vApp Author Global Role and publish it to an organization.
- Reversed result for the X-Large and Quad Large system resources functionalities in the Japanese version of the product
Due to a localization error in the Japanese version of vCloud Director, when you select option X-Large or Quad Large for the system resources of an edge gateway, the result is reversed.
- 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.
- Removing an external network from an edge gateway fails with an error message
On an edge gateway configured with more than one external networks, if you configure an Open Shortest Path First (OSPF) routing protocol, removing any of the external networks fails with an error message.
OSPF cannot be enabled on Vnic[s] without any configured subnets or if Vnic is disconnected. Please revisit OSPF configuration and retry., error code 13051
- Powering on a VM configured with an independent disk fails
If you attach an independent disk to a VM, powering on the VM fails with an error message.
Specified address is not in the subnet range.
Subsequent power on operations fail with a
NullPointer Exceptionerror message.
- Updating the VM properties by using the Flex UI changes the CPU and memory reservation settings from unlimited to zero
In an organization VDC configured with unlimited CPU and memory resources, using the Flex UI to update the properties of a VM changes the reservation pool settings for CPU and memory from unlimited to zero.
- 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-GCM as the encryption algorithm, viewing the properties of an edge gateway with enabled the IPsec VPN service fails with an error message.
Workaround: Use other encryption algorithm than the
- You cannot create a new standalone virtual machine that uses custom storage policy
In the vCloud Director Tenant Portal, when you create a new standalone VM by using a template and you select the custom storage policy option, the deployment of the VM fails with an error message.
HTTP 400 Bad Request
Workaround: To assign a custom storage policy to a new VM:
- Create the standalone VM on the default storage policy.
- After the standalone VM is created, edit the VM properties and change from default storage policy to a custom storage policy.