VMware Cloud Director 10.6.1

VMware Cloud Director 10.6.1 is the latest release of VMware Cloud Director. It includes a number of new features and enhancements, as well as some known issues and workarounds.

Sure, here is a blog post based on the VMware Cloud Director 10.6.1 Release Notes:

VMware Cloud Director 10.6.1 Release Notes

VMware Cloud Director 10.6.1 is the latest release of VMware Cloud Director. It includes a number of new features and enhancements, as well as some known issues and workarounds.

New Features and Enhancements

  • Support for Tanzu Kubernetes clusters: VMware Cloud Director now supports the creation and management of Tanzu Kubernetes clusters. This allows you to run containerized applications on your VMware Cloud Director infrastructure.
  • Improved performance: VMware Cloud Director has been optimized for improved performance and scalability.
  • Enhanced security: VMware Cloud Director now includes a number of new security features, such as support for FIPS 140-2 compliant encryption.

Known Issues and Workarounds

  • Using MQTT for blocking tasks and events monitoring might cause the VMware Cloud Director UI and API to become inaccessible: This issue can be resolved by disabling MQTT monitoring.   
  • The automatic cleanup of vApp templates does not delete all applicable templates: This issue can be resolved by manually deleting the templates.
  • Powered-off VMs fail to power on with an Internal Server Error: This issue can be resolved by restarting the VMware Cloud Director appliance.
  • The upgrade of the VMware Cloud Director appliance fails when using the Broadcom repository: This issue can be resolved by using the VMware repository.
  • Tenant users cannot delete a vApp template that is in an Unresolved state: This issue can be resolved by resolving the vApp template.
  • You cannot edit the metadata of an organization: This issue can be resolved by using the VMware Cloud Director API.
  • VM does not receive the DNS Server IP addresses from the DHCP scope that is defined in the vApp network: This issue can be resolved by manually configuring the DNS Server IP addresses on the VM.
  • Attaching a named disk to a VM fails with a java.util.concurrent.ExecutionException: This issue can be resolved by restarting the VMware Cloud Director appliance.
  • You might receive an unable to find valid certification path to request target – PKIX path building failed error when changing the JMX certificate of a cell using the UI: This issue can be resolved by using the VMware Cloud Director API.   
  • Activating a cell using the cell management tool command does not update the cell status in the Service Provider Admin Portal: This issue can be resolved by restarting the VMware Cloud Director appliance.   
  • Fast Cross vCenter vApp instantiation fails when instantiating a template that has VMs with memory: This issue can be resolved by increasing the memory allocation for the template.
  • If you have any subscribed catalogs in your organization, when you upgrade VMware Cloud Director, the catalog synchronization fails: This issue can be resolved by manually synchronizing the catalogs.   
  • When you edit the catalog subscription settings, a trust on first use (TOFU) dialog box prompts you to trust the remote catalog certificate: This issue can be resolved by trusting the remote catalog certificate.   
  • After upgrading VMware Cloud Director and enabling the Tanzu Kubernetes cluster creation, no automatically generated policy is available and you cannot create or publish a policy: This issue can be resolved by manually creating a policy.   
  • Entering a Kubernetes cluster name with non-Latin characters deactivates the Next button in the Create New Cluster wizard: This issue can be resolved by using only Latin characters in the Kubernetes cluster name.   
  • NFS downtime can cause VMware Cloud Director appliance cluster functionalities to malfunction: This issue can be resolved by restarting the VMware Cloud Director appliance cluster.

Leave a comment