VMware Cloud Director 10.4.3 | 9 JAN 2024 | Build 23065616 (installed build 23064643)

Check for additions and updates to these release notes.

What's New

VMware Cloud Director version 10.4.3 release includes the following:

  • VMware Cloud Director Encryption Management

    By using the VMware Cloud Director Encryption Management solution add-on to VMware Cloud Director, tenants can bring their own encryption keys (BYOK) and their own key management system (BYOKMS) when creating and encrypting virtual machines (VMs) within their respective virtual data centers (VDCs). The service providers set up connections to individual Key Management Servers (KMS), making the KMS accessible to organizations. Subsequently, the tenant administrator gains access to the KMS, goes through an authentication process, and allocates encryption keys to each of their VDCs. See the VMware Cloud Director Encryption Management Documentation.

  • HTTP Transparent Proxy

    This VMware Cloud Director release introduces the ability to configure custom API endpoints that redirect requests to a configurable HTTP endpoint that resides outside of VMware Cloud Director. This capability enables the implementation of UI and API extensions in VMware Cloud Director that accept requests from a user's browser or API client and communicate with another system that is reachable for VMware Cloud Director through HTTP, but it might not be accessible to users who are accessing VMware Cloud Director from the internet.

Product Support Notices

  • PostgreSQL 11 End of Life Notice

    The final release of PostgreSQL 11 occurred on November 9, 2023. PostgreSQL version 11 is currently unsupported. If you are using an external PostgreSQL configuration, consider upgrading to a later major version.

System Requirements and Installation

For information about system requirements and installation instructions, see VMware Cloud Director 10.4 Release Notes.

  • Supported NSX Advanced Load Balancer Versions

    VMware Cloud Director 10.4.3 supports NSX Advanced Load Balancer 20.1.7 and later versions. Earlier versions are not supported.

Documentation

To access the full set of product documentation, go to VMware Cloud Director Documentation.

Resolved Issues

  • New - Uploading a vApp template from an OVF fails with A specified parameter was not correct: profileId error

    When attempting to upload a vApp template from an OVF which contains both a StorageGroupSection and a BootOrderSection to a VDC backed by vCenter 8.0U2, the upload fails with the A specified parameter was not correct: profileId error. This problem can also occur when performing catalog synchronization or importing applications from VMware Marketplace into VMware Cloud Director. The problem occurs only on version 8.0U2 of vCenter.

  • New - New Web Console and VMware Remote Console (VMRC) connections might fail to connect intermittently with an HTTP 400 error

    The generated Web MKS ticket that VMware Cloud Director uses for remote console access to VMs might contain a double slash (//) which results in an incorrectly formed URL.

  • Provisioning of a new Tanzu Kubernetes Grid Service cluster might fail

    When attempting to provision a Tanzu Kubernetes Grid Service cluster, the operation might fail. The corresponding user task shows a status error message similar to the following.  

    [ <some unique id> ] An operation in vSphere for Kubernetes failed, reason message: Bad Request - admission webhook "default.validating.tanzukubernetescluster.run.tanzu.vmware.com" denied the request: Spec.Topology.ControlPlane.TKR.Reference.Name unable to resolve that TKR due to could not resolve TKR/OSImage for controlPlane, machineDeployments: [workers], query: {controlPlane: {k8sVersionPrefix: 'v1.23.8+vmware.3-tkg.1.ubuntu', tkrSelector: '', osImageSelector: 'os-name=photon'}, machineDeployments: [{k8sVersionPrefix: 'v1.23.8+vmware.3-tkg.1.ubuntu', tkrSelector: '', osImageSelector: 'os-name=photon'}]}, result: {controlPlane: {k8sVersion: '', tkrName: '', osImagesByTKR: map[]}, machineDeployments: [{k8sVersion: '', tkrName: '', osImagesByTKR: map[]}]} - Bad Request

    The problem is related to a vSphere Supervisor cluster API backward compatibility issue that breaks the integration with VMware Cloud Director. The compatibility is completely broken for with vSphere 8.x and later updates, and partially broken for vSphere 7.x updates.

  • Changing the primary IP address of an NSX edge gateway fails with a Cannot allocate multiple primary IP addresses for NSX-T Edge Gateway error

    When an NSX edge gateway has multiple IPv4 and IPv6 subnets, changing the primary IP address of the edge gateway fails with an error similar to the following.

    Error: [ e4dc8a76-86ea-408b-b2aa-27ea42305ec2 ] Cannot allocate multiple primary IP addresses for NSX-T Edge Gateway edgw1(com.vmware.vcloud.entity.gateway:8d17e279-2e4a-4452-b0c7-4a410a304374).
  • If you have a segment profile template configured for organization VDC networks, creating a direct network to an external network backed by distributed port groups fails with an Internal Server Error

    When you create a direct network to an external network backed by distributed port groups with a segment profile set for organization VDC networks, the creation fails with an Internal Server Error. The problem occurs because VMware Cloud Director is incorrectly trying to set segment profiles for the network backed by distributed port groups.

  • The VMware Cloud Director proxy does not work when the proxy is configured for a vCenter instance registered with a URL containing port 443

    When a vCenter instance is registered with a URL containing port 443, for example, https://vcenter.com:443, and you configure a proxy for that vCenter instance, VMware Cloud Director does not use the proxy and the java.net.SocketTimeoutException: connect timed out error appears in the logs.

  • VM does not receive the DNS Server IP addresses from the DHCP scope that is defined in the vApp network

    When you connect a VM to a routed vApp network in DHCP IP mode, the VM does not receive the DNS addresses defined in the DHCP scope.

  • In the Service Provider Admin Portal, the IP management UI shows wrong IP blocks to wrong ranges

    When you associate an edge gateway with a provider gateway with multiple subnets, and you navigate to the IP Allocation dialog box of the edge gateway, the primary IP address appears as part of an incorrect subnet.

  • After startup, VMware Cloud Director services fail continuously with an java.lang.OutOfMemoryError: Java heap space error

    The problem can occur when the resolve operation is invoked on a Runtime Defined Entity (RDE) which has a large number of tasks associated with it. As a result, the /opt/vmware/vcloud-director/logs/cell-runtime.log on VMware Cloud Director cells shows errors similar to the following:

    FATAL    | ... | UncaughtExceptionHandlerStartupAction | Uncaught Exception. Originating thread: Thread[...]. Message: Java heap space |java.lang.OutOfMemoryError: Java heap space

    In addition, VMware Cloud Director generates and presents Java .hprof files in the /opt/vmware/vcloud-director/logs/ directory of the cells.

    See KB article 95464.

  • vApp deployments from a vApp template might fail with Error: com.vmware.pbm.placement.PlacementException: PlacementException NO_FEASIBLE_PLACEMENT_SOLUTION

    When you try to deploy a vApp from a vApp templete, the deployment might fail even when the datastore has enough hard disk space. The vcloud-container-debug.log might contain an event similar to the following.

    java.lang.IllegalArgumentException: Container moref://<UUID>/Datastore#datastore-1234 has usedCapacityMb: 5908851 > totalCapacityMb: 5242624

  • Copying a powered on virtual machine with multiple NICs to a vApp fails with a Internal Server error message

    When attempting to copy a powered on VM with multiple NICs to a vApp, if you select the option to reset the MAC addresses of all NICs, the operation fails with an Internal Server error message.

  • An attempt to configure additional routing services on an edge gateway that has a dedicated provider gateway fails with a Routing configuration is not supported for edge error message

    If an edge gateway has a dedicated provider gateway and can connect to an external network, configuring additional routing services on this edge gateway, such as route advertisement and border gateway protocol (BGP) configuration, fails with the following error message.

    Routing configuration is not supported for edge

  • If you shut down the guest OS before deleting a VM, VMware Cloud Director cannot reuse the VM's IP address from the static pool of IP addresses

    If you shut down the guest OS of a VM with a static pool IP allocation before deleting the VM, VMware Cloud Director does not release the IP address back into the IP pool, resulting in IP exhaustion. Creating a scale group or a VM with this IP address might fail with the following error.

    No Static IP Pools or no free IP within any Static IP Pool to allocate to VM nic at index 0.
  • Modified - All VM consoles disconnect after one minute

    When a system user opens the Web Console or the VMware Remote Console (VMRC), after one minute, the console automatically closes. Because the Web Console always retries to connect after a disconnect, this problem might stay unnoticed, but a console you open through VMRC remains disconnected. The problem occurs because the monitoring that ends VM console sessions for deactivated users incorrectly ends the VM console sessions of all service provider users after the default interval of one minute.  The problem does not affect tenant users of VMware Cloud Director.

Known Issues

  • New - VMware Cloud Director backup fails

    If you use Ubuntu or Linux distributions that are based on Debian as NFS for the VMware Cloud Director appliance, the NFS server cannot be configured appropriately to support the creation of backups through the PostgreSQL user.

    Workaround: Depending on the file that the appliance has, run the following commands from appliance's secure shell as the root user.

    • If the appliance has the /opt/vmware/appliance/bin/create-db-backup file, run the following command.

    sed -i '/PG_BACK_UP() {/,/}/ { /PG_BACK_UP() {/!{ /}/!d }}; /PG_BACK_UP() {/ a\su - postgres -c "$VMWARE_POSTGRES_BIN\/pg_dump -v -Fc \$DBNAME" > \$DB_DUMP_PATH 2>> \$LOG_FILE' /opt/vmware/appliance/bin/create-db-backup

    • If the appliance has the /opt/vmware/appliance/bin/create-backup.sh file, run the following commands.

    sed -i '/DB_BACKUP() {/,/}/ { /DB_BACKUP() {/!{ /}/!d }}; /DB_BACKUP() {/ a\su - postgres -c "$VMWARE_POSTGRES_BIN\/pg_dump -v -Fc \$DBNAME" > \$DB_DUMP_PATH 2>> \$LOG_FILE' /opt/vmware/appliance/bin/create-backup.sh

    sed -i '/DB_USER_BACKUP() {/,/}/ { /DB_USER_BACKUP() {/!{ /}/!d }}; /DB_USER_BACKUP() {/ a\su - postgres -c "$VMWARE_POSTGRES_BIN\/pg_dumpall --roles-only | grep -e '\''CREATE ROLE vcloud;\\|ALTER ROLE vcloud WITH'\''" > \$BACKUP_DIR\/vcloud-user.sql' /opt/vmware/appliance/bin/create-backup.sh

  • New - After reverting a virtual machine to a snapshot, the guest operating system does not automatically roll back to a previous version

    If you upgrade the guest operation system of a virtual machine after taking a snapshot, after reverting to the snapshot, the guest operation system does not automatically roll back to a previous version.

    Workaround: None.

  • New - Any update to a VM triggers a relocation even when the current location can still accommodate the VM

    The issue occurs because of missing per-disk datastore requirements that also pin the disks.

    Workaround: Deactivate Storage DRS.

  • New - After upgrading a VMware Cloud Director appliance, the management API and the management UI report an incorrect older version of the appliance

    The problem occurs because the VMware Cloud Director appliance management API uses a different source of truth for obtaining the current version of the VMware Cloud Director appliance than the vamicli version --appliance command. This alternate source of truth is not always being updated during the appliance upgrade causing incorrect information to appear.

    Workaround: Use the vamicli version --appliance command to verify the VMware Cloud Director appliance version.

  • New - When you deploy a VM from a template with a storage policy that includes a configured IOPS limit, after deployment, the VM disks do not have an IOPS limit configured or have a different IOPS limit

    The problem occurs because the the I/O Operations Per Second (IOPS) limit set in the VM template overrides the storage policy's IOPS limit. For example, if the VM template does not have a configured IOPS value, after deployment, the VM disks do not have a configured IOPS limit.

    Workaround: You can use vApp templates, or edit the VM after deployment.

  • New - VMware Cloud Director assigns the vGPU policy to a newly deployed virtual machine tagged with the general purpose policy

    If you add a newly deployed virtual machine to a vApp and you tag the virtual machine with the general purpose policy, VMware Cloud Director assigns the vGPU policy instead.

    Workaround: None.

  • New - When sharing vApps with users, you can navigate to nonexistent pages

    When sharing vApps with users, the buttons to go to the previous or next page are available even though you are already on the respective first or last page. As a result, you can navigate to pages that do not exist and do not have content.

    Workaround: None.

  • New - If you create a vApp network while copying a VM, when you close the Copy VM modal, an infinity spinner appears

    When you copy VMs to a target vApp, if you create a new vApp network in the target vApp and connect the source VMs to the newly created target vApp's network, closing the modal causes the spinner to appear, but it does not disappear once the copy operation is completed. This problem occurs only when a new vApp network is created during the copy process and does not occur when you copy VMs without creating a vApp network.

    Workaround: Navigating to another page and returning to the VM list reloads the grid and the spinner disappears.

  • New - The VMware Cloud Director API does not return some provider VDCs as merge candidates

    If you attempt to get merge candidates for a provider VDC and there are more provider VDCs in the system than the value specified in the page size query parameter, the merge candidate API only processes the first page size number of provider VDCs to check if they are merge candidates and ignores the other provider VDCs in the system.

    Workaround: To ensure the VMware Cloud Director API processes all the provider VDCs, specify a page size greater than or equal to the number of provider VDCs in the system.

  • New - Attempting to modify the port for the NSX Edge load balancer pool fails with an INTERNAL_SERVER_ERROR

    After you delete a virtual service, trying to update the pool which was previously connected to the deleted virtual service fails with an INTERNAL_SERVER_ERROR. For example, changing the port for the pool fails.

    Workaround: None.

  • New - Deleting an organization in VMware Cloud Director UI fails with a You must delete this Organization's Application Port Profiles before you can delete the organization error

    If application port profiles are created on an edge gateway associated with an organization, attempting to delete the organization fails. The issue occurs because VMware Cloud Director deletes the edge gateways before deleting the port profiles, which causes the following error.

    com.vmware.vcloud.api.presentation.service.InvalidStateException: You must delete this Organization's Application Port Profiles before you can delete the organization.

    Workaround: Use the VMware Cloud Director API to force delete an organization and to delete the stranded application port profiles associated with it. See Delete Stranded Application Port Profiles from VMware Cloud Director.

  • New - You cannot access the Service Provider Admin Portal and the VMware Cloud Director Tenant Portal after rebooting the VMware Cloud Director VM

    If you reboot the VMware Cloud Director VM by using a method other than using the vSphere Client, for example, by using vSphere High Availability or VMware Host Client, you cannot access the Service Provider Admin Portal and the VMware Cloud Director Tenant Portal. The problem occurs because after the reboot, the deployment OVF parameters are deleted from the ovfEnv.xml file, and the cell cannot be accessed.

    Workaround: Power off and then power on the VMware Cloud Director VM by using the vSphere Client.

  • New - You cannot edit the metadata of an organization

    If you use the VMware Cloud Director API to create two metadata entries for an organization using the same name for the entries, you cannot edit these metadata entries by using the UI because the Save button in the Edit Metadata wizard is not active.

    Workaround: Use the VMware Cloud Director API to edit the name of one of the metadata entries.

  • New - Using the VMware Cloud Director API, attempting to delete an item with a secure field from an array in an RDE instance results in the item not being fully deleted

    If an RDE type schema contains an array object with items containing secure fields, trying to remove an item of the array from an RDE instance of that type through an RDE PUT call results in all fields in the item being deleted except for the secure fields. The item itself is not removed. The problem occurs when you use VMware Cloud Director API version 37.3 or earlier.

    If the RDE instance is in RESOLVED state and if after the update the entity contents of the instance do not match the schema in the RDE type of the instance, the PUT call results in an error response with status code 400 and error message RDE_CANNOT_VALIDATE_AGAINST_SCHEMA. If the entity contents of the instance after the update match the schema in the RDE type of the instance, the call does not return an error despite the item not being fully deleted.

    Workaround: None.

  • API clients throw Invalid mime type errors for responses from multisite VMware Cloud Director APIs

    If the multisite field in the response header values specifies a list of organizations, the API client generates the following error.

    org.springframework.util.InvalidMimeTypeException: Invalid mime type 

    The issue occurs because the VMware Cloud Director API returns an illegal @ character in the MIME (Multipurpose Internet Mail Extensions) type headers of the response. You can ignore the error because VMware Cloud Director continues to function properly.

    Workaround: None.

  • You cannot perform Solution Add-On instance operations, such as remove, upgrade, retry, and rollback

    Updating Runtime Defined Entities (RDE) that contain restricted fields might fail if you remove an item from an array in the entity contents. This RDE problem causes Solution Add-On operations, such as remove, upgrade, rollback, and retry to fail with the following error.

    RDE_CANNOT_VALIDATE_AGAINST_SCHEMA [ #/resources/xxx: expected type: JSONObject, found: Null

    Workaround: None.

  • Updating a Runtime Defined Entity (RDE) that contains restricted fields might fail if you remove an item from an array in the entity contents

    Defined entity types might specify restricted fields in their JSON schema using the x-vcloud-restricted property. If a defined entity instance is of a type that specifies such restricted fields and also contains arrays, removing an item in an array might cause the RDE updates to fail with a NullPointerException.

    Workaround: Instead of removing the array item, replace it with {}. Alternatively, remove the entire array in one update and then add it with the new data in another update. However, if you add the array with the new data, VMware Cloud Director does not validate the restricted fields in the array against their access and encryption specifications.

  • When starting the VMware Cloud Director appliance, the message [FAILED] Failed to start Wait for Network to be Configured. See 'systemctl status systemd-networkd-wait-online.service' for details appears

    The message appears incorrectly and does not indicate an actual problem with the network. You can disregard the message and continue to use the VMware Cloud Director appliance as usual.

    Workaround: None.

  • Upgrading to VMware Cloud Director 10.4.1 or later fails with a Fix postgres user home directory error

    When you try to upgrade to VMware Cloud Director 10.4.1 or later, the upgrade fails. The update-postures-db.log contains the following error.

    2023-05-15 16:38:01 | update-postgres-db.sh | Fix postgres user home directory
    usermod: user postgres is currently used by process 17236

    Other processes that are logged in as the postgres user on the VMware Cloud Director appliance might block the script that upgrades the PostgreSQL major version from 10 to 14.

    Workaround:

    1. Before starting the VMware Cloud Director upgrade, find any processes that are logged in as the postgres user on the VMware Cloud Director appliance by running ps -u postgres on the appliance.

    2. Stop any process that the command returns by running kill -9 <PID>, where PID is the unique process identifier.

  • The VMware Cloud Director appliance database disk resize script might fail if the backing SCSI disk identifier changes

    The database disk resize script runs successfully only if the backing database SCSI disk ID remains the same. If the ID changes for any reason, the script might appear to run successfully but fails. The /opt/vmware/var/log/vcd/db_diskresize.log shows that the script fails with a No such file or directory error.

    Workaround:

    1. Log in directly or by using an SSH client to the primary cell as root.

    2. Run the lsblk --output NAME,FSTYPE,HCTL command.

    3. In the output, find the disk containing the database_vg-vpostgres partition and make note of its ID. The ID is under the HCTL column and has the following sample format 2:0:3:0.

    4. In the db_diskresize.sh script, modify the partition ID with the ID from Step 3. For example, if the ID is 2:0:3:0, in line

      echo 1 > /sys/class/scsi_device/2\:0\:2\:0/device/rescan

      you must change the ID to 2:0:3:0.

      echo 1 > /sys/class/scsi_device/2\:0\:3\:0/device/rescan
    5. Аfter saving the changes, manually re-invoke the resize script or reboot the appliance.

  • Creating an organization VDC template with NSX network provider type and provider gateways that uses IP spaces fails

    When you attempt to create an organization VDC template with NSX network provider type and provider gateway that uses IP spaces, the operation fails with the following error. Error:Cannot support external Network that is utilizing IP Spaces. Only external networks with legacy IP blocks are supported.

    Workaround: Create organization VDC templates with NSX network provider type and provider gateways that use legacy IP blocks.

  • Changing the storage policy on a virtual disk of a VM fails with a The operation failed because no suitable resource was found error message

    If the virtual disk of a VM resides on a remote vSAN datastore, changing the storage policy of the virtual disk results in an error message.

    The operation failed because no suitable resource was found

    Workaround: To move the VM to a different storage policy, change the virtual disk storage policy to VM default policy and then change the VM storage policy to the desired storage policy.

  • VMware Cloud Director shows an empty value for the IOPS limit for a VM disk with VC-IOPS enabled storage policy

    If you apply a VC-IOPS enabled storage policy with custom reservation, limit, and shares, on a VM disk, VMware Cloud Director displays the values for IOPS reservations, but displays the IOPS limit as empty. This happens because vCenter Server 8U1 introduces a new mechanism for Storage I/O Control (SIOC) which no longer sets the IOPS limit as a VM disk property.

    Workaround: None.

  • You cannot create a disabled organization using the legacy VMware Cloud Director API

    Attempting to use the legacy VMware Cloud Director API organization creation endpoint POST [vcd_public_endpoint]/api/admin/orgs to create a disabled organization results in a 400 BadRequestException containing the following snippet:

    <Error ... stackTrace="com.vmware.vcloud.api.presentation.service.BadRequestException: Unexpected error.&#10;unexpected end of subtree

    Workaround: Use the VMware Cloud Director OpenAPI endpoint to create a disabled organization. Alternatively, you can use the UI, OpenAPI, or legacy API to create an enabled organization and disable it after creation.

  • Creating an organization VDC Kubernetes policy with provider gateways that uses IP spaces fails

    If you configure an IP space backed provider gateway and you create a VDC and an edge gateway based on the same IP space, an attempt to create a Kubernetes policy for this VDC fails with an error message.

    com.vmware.ssdc.util.LMException: Index 0 out of bounds for length 0

    This happens because the IP space backed edge gateways are not associated with a primary IP address, which is required for the creation of SNAT by the Kubernetes policy.

    Workaround: Create VDC and edge gateways with NSX network provider type and provider gateways that use legacy IP blocks.

  • If you try to restore the VMware Cloud Director appliance with the console proxy certificates, the restore fails

    In the VMware Cloud Director appliance management UI, if you want to restore the appliance and select the Console Proxy check box under Select the certificates to be restored on to this node from the selected backup, the restore fails.

    Workaround: Starting with version 10.4, the console proxy and REST API use a single certificate. In version 10.4.1 and later, the legacy console proxy implementation is not supported and selecting the check box is not necessary. Repeat the restore procedure without selecting the Console Proxy check box.

  • You cannot select Tanzu Kubernetes version 2.0 or later when creating a TKGs cluster

     As a tenant, when attempting to create a TKGs cluster, you cannot select a Tanzu Kubernetes cluster version 2.0 and later. 

    Workaround: To offer and use Tanzu Kubernetes 2.0 and later, use VMware Cloud Director Container Service Extension 4.0.

  • Migrating VMs between organization VDCs might fail with an insufficient resource error

    If VMware Cloud Director is running with vCenter Server 7.0 Update 3h or earlier, when relocating a VM to a different organization VDC, the VM migration might fail with an insufficient resource error even if the resources are available in the target organization VDC.

    Workaround: Upgrade vCenter Server to version 7.0 Update 3i or later.

  • The VMware Cloud Director Tenant Portal UI does not display the IOPS limits and reservations for a vSAN storage policy

    vSAN manages itself the IOPS limits on vSAN storage policies. As a result, the VMware Cloud Director Tenant Portal UI does not display the IOPS reservations and limits for a vSAN storage policy and you cannot modify their values.

    Workaround: None.

  • VMware Cloud Director appliance upgrade fails with an invalid version error when FIPS mode is enabled

    For VMware Cloud Director versions 10.3.x and later, when FIPS mode is enabled, VMware Cloud Director appliance upgrade fails with the following error.

    Failure: Installation failed abnormally (program aborted), the current version may be invalid.

    Workaround:

    1. Before you upgrade the VMware Cloud Director appliance, deactivate FIPS Mode on the cells in the server group and the VMware Cloud Director appliance. See Activate or Deactivate FIPS Mode on the VMware Cloud Director Appliance.

    2. Verify that the /etc/vmware/system_fips file does not exist on any appliance.

    3. Upgrade the VMware Cloud Director appliance.

    4. Enable FIPS mode again.

  • Restore from an appliance backup might fail with an Invalid command-line arguments. Missing argument for option: consoleproxy-cert error

    If you run the clear-console-proxy-settingsCMT command before you take an appliance backup, then, if you choose to restore the console proxy certificate from the backup, the restore process fails with an Invalid command-line arguments. Missing argument for option: consoleproxy-cert error.

    The issue occurs because the command to clear the console proxy settings removes the console proxy certificate, and the console proxy settings are missing for the backup. If the console proxy certificate is not in the backup, you cannot restore it.

    Workaround: If the console proxy settings were cleared, run the appliance restore without selecting to restore the console proxy certificate.

  • You can't view and edit the license type for your previously registered NSX Advanced Load Balancer Controller instances in the VMware Cloud Director API

    You can't view and edit the license for your previously registered NSX Advanced Load Balancer Controller instances in the VMware Cloud Director API. This happens because in VMware Cloud Director 10.4, the Controller license type was replaced by a selection between a Standard and a Premium feature set at the Service Engine Group level to provide more flexibility.

    Workaround: Use the supportedFeatureSet path for service engine groups and on edge gateways to activate and deactivate the available features.

  • You cannot create and use VMware Cloud Director VDC templates in VMware Cloud Director service environments that use VMware Cloud on AWS network pools

    If you are using only a provider network pool that is backed by VMware Cloud on AWS for your provider VDC, you cannot create a VDC template and instantiate a VDC from a template. This happens because creating and instantiating VDC templates is supported only for provider VDCs backed by NSX-T Data Center and by NSX Data Center for vSphere. You can use VMware Cloud Director VDC templates with on-premises, Microsoft Azure VMware Solution, Oracle Cloud VMware Solution, or Google Cloud VMware Engine SDDCs.

    Workaround: None.

  • Creating a new VM with encrypted vSAN storage policy fails with an Invalid storage policy for encryption operation error message

    When creating a new VM, if you specify the storage policy of the VM as vSAN encrypted and the storage policy for the VM hard disk as both non-encrypted and non-vSAN, the operation fails with an error message.

    Invalid storage policy for encryption operation

    Workaround:

    1. Specify the storage policies for the VM and the VM hard disk as vSAN encrypted.

    2. After the VM deploys successfully, update the hard disk storage policy for the VM to non-encrypted and non-vSAN. For information, see Edit Virtual Machine Properties.

  • You cannot connect to VMware Cloud Director through VMware OVF Tool version 4.4.3 or earlier

    When you attempt to connect to VMware Cloud Director through OVF Tool version 4.4.3 or earlier, this results in the following error. Error: No supported vCloud version was found. This happens because of an API behavior change in VMware Cloud Director 10.4 where the API does not return links to all the VDCs in an organization.

    Workaround: Upgrade to OVF Tool 4.5.0. See VMware OVF Tool Release Notes.

  • You are unable to log in to VMware Cloud Director by using VMware PowerCLI 12.7.0 or earlier

    When you attempt to log in to VMware Cloud Director by using VMware PowerCLI version 12.7.0 or earlier, this results in the following error. NOT_ACCEPTABLE: The request has invalid accept header: Invalid API version requested. This happens because VMware PowerCLI earlier than 13.0.0 do not support VMware Cloud Director API versions later than 33.0. See VMware Product Interoperability Matrix.

    Workaround: Upgrade VMware PowerCLI to version 13.0.0.

  • VMware Cloud Director displays the old version for an upgraded vCenter Server instance

    After you upgrade a vCenter Server instance to a newer version, in the list of vCenter Server instances, VMware Cloud Director still displays the old version for the upgraded instance.

    Workaround: Reset the connection between the vCenter Server instance and VMware Cloud Director. See Reconnect a vCenter Server Instance in VMware Cloud Director Service Provider Admin Portal Guide.

  • Refreshing the LDAP page in your browser does not take you back to the same page

    In the Service Provider Admin Portal, refreshing the LDAP page in your browser takes you to the provider page instead of back to the LDAP page.

    Workaround: None.

  • Mounting an NFS datastore from NetApp storage array fails with an error message during the initial VMware Cloud Director appliance configuration

    During the initial VMware Cloud Director appliance configuration, if you configure an NFS datastore from NetApp storage array, the operation fails with an error message.

    Backend validation of NFS failed with: is owned by an unknown user

    Workaround: Configure the VMware Cloud Director appliance by using the VMware Cloud Director Appliance API.

  • The synchronization of a subscribed catalog times out while synchronizing large vApp templates

    If an external catalog contains large vApp templates, synchronizing the subscribed catalog with the external catalog times out. The issue occurs when the timeout setting is set to its default value of five minutes.

    Workaround: Using the manage-config subcommand of the cell management tool, update the timeout configuration setting.

    ./cell-management-tool manage-config -n transfer.endpoint.socket.timeout -v [timeout-value]

  • In an IP prefix list, configuring any as the Network value results in an error message

    When creating an IP prefix list, if you want to deny or accept any route and you configure the Network value as any, the dialog box displays an error message.

    "any" is not a valid CIDR notation. A valid CIDR is a valid IP address followed by a slash and a number between 0 and 32 or 64, depending on the IP version.

    Workaround: Leave the Network text box blank.

  • The vpostgres process in a standby appliance fails to start

    The vpostgres process in a standby appliance fails to start and the PostgreSQL log shows an error similar to the following. FATAL: hot standby is not possible because max_worker_processes = 8 is a lower setting than on the master server (its value was 16). This happens because PostgreSQL requires standby nodes to have the same max_worker_processes setting as the primary node. VMware Cloud Director automatically configures the max_worker_processes setting based on the number of vCPUs assigned to each appliance VM. If the standby appliance has fewer vCPUs than the primary appliance, this results in an error.

    Workaround: Deploy the primary and standby appliances with the same number of vCPUs.

  • Upgrading from VMware Cloud Director 10.3.x to VMware Cloud Director 10.4.x results in an Connection to sfcbd lost error message

    If you upgrade from VMware Cloud Director 10.3.x to VMware Cloud Director 10.4.x, the upgrade operation reports an error message.

    Connection to sfcbd lost. Attempting to reconnect

    Workaround: You can ignore the error message and continue with the upgrade.

  • When using FIPS mode, trying to upload OpenSSL-generated PKCS8 files fails with an error

    OpenSSL cannot generate FIPS-complaint private keys. When VMware Cloud Director is in FIPS mode and you try to upload PKCS8 files generated using OpenSSL, the upload fails with a Bad request: org.bouncycastle.pkcs.PKCSException: unable to read encrypted data: ... not available: No such algorithm: ...error or salt must be at least 128 bits error.

    Workaround: Deactivate the FIPS mode to upload the PKCS8 files.

  • Creation of Tanzu Kubernetes cluster by using the Kubernetes Container Clusters plug-in fails

    When you create a Tanzu Kubernetes cluster by using the Kubernetes Container Clusters plug-in, you must select a Kubernetes version. Some of the versions in the drop-down menu are not compatible with the backing vSphere infrastructure. When you select an incompatible version, the cluster creation fails.

    Workaround: Delete the failed cluster record and retry with a compatible Tanzu Kubernetes version. For information on the incompatibilities between Tanzu Kubernetes and vSphere, see Updating the vSphere with Tanzu Environment.

  • If you have any subscribed catalogs in your organization, when you upgrade VMware Cloud Director, the catalog synchronization fails

    After upgrade, if you have subscribed catalogs in your organization, VMware Cloud Director does not trust the published endpoint certificates automatically. Without trusting the certificates, the content library fails to synchronize.

    Workaround: Manually trust the certificates for each catalog subscription. When you edit the catalog subscription settings, a trust on first use (TOFU) dialog prompts you to trust the remote catalog certificate.

    If you do not have the necessary rights to trust the certificate, contact your organization administrator.

  • 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

    When you upgrade VMware Cloud Director to version 10.3.1 and vCenter Server to version 7.0.0d or later, and you create a provider VDC backed by a Supervisor Cluster, VMware Cloud Director displays a Kubernetes icon next to the VDC. However, there is no automatically generated Kubernetes policy in the new provider VDC. When you try to create or publish a Kubernetes policy to an organization VDC, no machine classes are available.

    Workaround: Manually trust the corresponding Kubernetes endpoint certificates. See VMware knowledge base article 83583.

  • Entering a Kubernetes cluster name with non-Latin characters deactivates the Next button in the Create New Cluster wizard

    The Kubernetes Container Clusters plug-in supports only Latin characters. If you enter non-Latin characters, the following error appears.

    Name must start with a letter and only contain alphanumeric or hyphen (-) characters. (Max 128 characters).

    Workaround: None.

  • NFS downtime can cause VMware Cloud Director appliance cluster functionalities to malfunction

    If the NFS is unavailable due to the NFS share being full, becoming read only, and so on, can cause appliance cluster functionalities to malfunction. HTML5 UI is unresponsive while the NFS is down or cannot be reached. Other functionalities that might be affected are the fencing out of a failed primary cell, switchover, promoting a standby cell, and so on. For more information about setting up correctly the NFS shared storage, see Preparing the Transfer Server Storage for the VMware Cloud Director Appliance.

    Workaround: 

    • Fix the NFS state so that it is not read-only.

    • Clean up the NFS share if it is full.

  • Trying to encrypt named disks in vCenter Server version 6.5 or earlier fails with an error

    For vCenter Server instances version 6.5 or earlier, if you try to associate new or existing named disks with an encryption enabled policy, the operation fails with a Named disk encryption is not supported in this version of vCenter Server. error.

    Workaround: None.

  • A fast-provisioned virtual machine created on a VMware vSphere Storage APIs Array Integration (VAAI) enabled NFS array, or vSphere Virtual Volumes 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 vSphere Virtual Volumes. 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 vSphere Virtual Volumes. To consolidate a virtual machine with a snapshot on a VAAI or a vSphere Virtual Volumes datastore, relocate the virtual machine to a different storage container.

  • If you add an IPv6 NIC to a VM and then you add an IPv4 NIC to the same VM, the IPv4 north-south traffic breaks

    Using the HTML5 UI, if you add an IPv6 NIC first or configure an IPv6 NIC as the primary NIC in a VM, and then you add an IPv4 NIC to the same VM, the IPv4 north-south communication breaks.

    Workaround: First you must add the IPv4 NIC to the VM and then the IPv6 NIC.

check-circle-line exclamation-circle-line close-line
Scroll to top icon