vCloud Director 22.214.171.124 for Service Providers | 5 SEP 2019 | Build 14535248 (installed build 14534864)
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.7.x for Service Providers
- Resolved Issues
- Known Issues
The vCloud Director 126.96.36.199 for Service Providers Express Patch Release provides bug fixes, updates the vCloud Director appliance base OS and the vCloud Director open-source components. The release resolves CVE-2019-11477 and CVE-2019-11478, for more information see https://www.vmware.com/security/advisories.
For more information about system requirements and installation instructions, see vCloud Director Installation and Upgrade Guide.
To access the full set of product documentation, go to VMware vCloud Director for Service Providers Documentation.
- New The vCloud Director appliance log files are consuming excess amount of storage space
auth.logautomatic log rotation is not set up, the vCloud Director appliance displays an
Insufficient free disk space in the / partition.error.
- New Existing organization VDC networks that are operational are showing non-operational status in the vCloud Director tenant portal
If you upgrade to vCloud Director 188.8.131.52 or to vCloud Director 184.108.40.206, and you have organization VDC networks that you have not modified in the last month, the networks show a red operational status instead of green.
- During vCloud Director Appliance deployment, attempting to set a static route via the provided OVF parameters fails
During vCloud Director Appliance deployment, attempting to set a static route via the provided OVF parameters fails. Error messages related to inaccessible system directories appear in the
# cat /opt/vmware/var/log/vcd/networkconfig.log
find: './proc/852': No such file or directory
find: './proc/853': No such file or directory
find: './proc/854': No such file or directory
- In a multi-cluster environment backed by a Provider VDC, shared networks appear as duplicate networks
When you configure a multi-cluster environment backed by a provider VDC and you navigate to the organization VDC networks, you see shared organization VDC networks as duplicate.
- Unable to attach an additional external network to an edge gateway, when the same edge is used as an egress point
If data center group or a stretch network already uses a particular edge gateway as an egress point, you cannot attach an additional external network to it and you receive an error message.
Vnic indexes should be unique. Multiple Vnics have same index 0.
- vApp Authors and vApp Users cannot edit routed vApp networks in the vCloud Director tenant portal
In the vCloud Director tenant portal, a vApp Author or a vApp User navigates to My Cloud > vApp, selects a vApp, clicks Open and on the Networking tab navigates to the properties of a vApp network. When the vApp Author or vApp User tries to modify the settings of the selected routed vApp network they receive an
HTTP 400 Bad Requesterror message.
- Searching a vApp template by either name, catalog or owner fails
In the vCloud Director tenant portal under Libraries > vApp templates when you try to filter the vApp templates by name, catalog or owner, the search query fails with
HTTP 400 Bad Requesterror message.
- Creating a new virtual machine with Flexible virtual network adapter type is not displayed properly in REST API response
Creating a new virtual machine with Flexible virtual network adapter type is shown as
PCNet32in the REST API response.
- NSX-v backed network pools are available for use when creating NSX-T backed organization VDCs in the HTML UI
In a vCloud Director environment where NSX-V and NSX-T coexist, when you create an organization VDCs backed by an NSX-T instance in the vCloud Director tenant portal those network pools that are backed by NSX-V are also available for selection.
- Virtual machine that is imported from a vCenter Server resource pool to a vCloud Director, shows invalid state after updating the storage policy
You import a virtual machine from a vCenter Server resource pool to a vCloud Director. After updating the storage policy of the imported virtual machine, its status appears as
Invalidunder the Hosts and Clusters drop down menu in the vSphere Client.
- The IP address list in the Edit Virtual Server menu is empty
You add a virtual server to a load balancer in edge gateway. When you try to edit the settings of the virtual server, the IP Address list in the Select IP address wizard is empty.
- In vSphere Client, you cannot assign a custom IP address to a virtual server
When you try to add a virtual server to an edge gateway, from the pre-configured suballocated pool with IPv6 addresses you can select only the primary IPv6.
- You cannot assign a computer name to newly created virtual machine from a template
After you create a standalone virtual machine from a template, the assigned virtual machine name after creation uses the default template name, instead of the name you entered.
- Log in to the vCloud Director Web Console by using a SAML authentication, resolved an incorrect URL
When you try to log in to the vCloud Director Web Console, and you use SAML authentication, the resolved URL references to
- Newly added network interface to a virtual machine is not connected
In vCloud Director portal, when you add a new network interface to a virtual machine, the Connected check box for the NIC is not connected by default. To configure for the new NIC to have network connection, you must manually select the Connected check box.
- Synchronization between vCenter Server and vCloud Director might take very long to complete
In the vCloud Director Web Console, you navigate to the System > vCenters list and you try to reconnect a vCenter Server to vCloud Director by right-click on the vCenter Server and selecting Reconnect. The reconnect might take very long time to complete.
- In the vCloud Director Web Console, you cannot suballocate IP pools on an edge gateway
In the vCloud Director Web Console, when you navigate to Edge Gateways > Properties > Sub-Allocate IP Pools and you try to suballocate an IP address on an advanced edge gateway, you receive a
- When you edit a IPsec VPN service, that is configured between two organization VDC Edge Gateways, the CA certificate is removed from the IPsec VPN configuration
Editing an IPsec configuration with enabled certificate authentication, removes the CA certificate and you cannot establish the tunnel between the two organization VDC edge gateways.
- 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.
- The IOPS allocation value of a resulted vApp from a vApp template is 0
When you try to instantiate new vApp using vApp template, instead of assigning the IOPS allocation value that was set up in the vApp template, the resulted vApp takes the storage value from the vCenter Server. The IOPS value of the newly created vApp is 0.
- Updating the properties of a shared direct organization VDC network in the tenant portal H5 UI causes it to be unshared if not in use by a VM or vApp, or causes it to fail, if in use by a VM or vApp.
When trying to update the name or description of a shared direct organization VDC network on the tenant portal H5 UI, if the network is shared and not in use, it becomes unavailable to other VDCs in the organization. If the network is in use, it fails with an error message saying that the network is in use. This is because the UI is not sending the shared flag and triggers an unsharing operation.
Workaround: Update properties of a direct organization VDC network through the Flex UI.
- Promoting a standby cell to become a primary cell in a high availability cluster might result in an Nginx error screen
If a primary or a standby cell is offline at the moment when you attempt to promote a standby cell to become the new primary cell using the appliance management user interface, this might result in the following error message in your browser:
"An error occurred. Sorry, the page you are looking for is currently unavailable. Please try again later. If you are the system administrator of this resource then you should check the error log for details. Faithfully yours, nginx."
Workaround: Refresh your browser.
- 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.
- 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
UiBrandingLinkthat 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
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:
- 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.
- In vCloud Director Web console, 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 delete the organization VDC network, click Apply.
- In vCloud Director Web console, navigate to System > Organizations, and select your organization name.
- 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.
- 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).
- Newly created virtual machine is 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.