RSS
 

VMware Cloud Director 10.4.2.2 | 21 SEP 2023 | Build 22465258 (installed build 22463311)

Check for additions and updates to these release notes.

What's New

VMware Cloud Director version 10.4.2.2 release includes the following:

Product Support Notices

  • New - 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.

Documentation

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

Resolved Issues

  • New - The screen resolution of a virtual machine Web console in full screen mode does not adapt automatically to the screen size

    When opening the Web console of a VM in full screen mode, the console resolution does not automatically adjust to match the screen size.

  • New - An attempt to view the task details for a deleted item as a user with custom role fails with a This operation is denied error message

    In VMware Cloud Director Tenant Portal, if you login as a user with custom role that includes Administrator View rights and no manage rights, an attempt to view the task details for a deleted item by another user fails with an error message.

    This operation is denied

  • VMware Cloud Director fails to assisgns the default organization VDC storage policy when creating a new VM from a template

    When creating a new VM from a template, instead of assigning the default organization VDC storage policy, VMware Cloud Director assigns the first storage policy from an alphabetized storage policy list available to the organization.

  • An attempt to update a VM property fails with a The operation failed because no suitable resource was found error message

    In an environment where you configure an organization that has VDCs backed by multiple vCenter Server instances and you group these VDCs, if a VM is attached to the VDC group network, an attempt to edit the VM fails with an error message.

    The operation failed because no suitable resource was found. Out of 1 candidate hubs: 1 hubs eliminated because: No access to network <network-name>. Rejected hubs: resgroup-1015 - PlacementException NO_FEASIBLE_PLACEMENT_SOLUTION

  • The VMware Cloud Director API query for user privileges on a set of entities and user granted privileges returns incorrect results

    If an imported user is assigned the Defer to Identity Provider role and you run the VMware Cloud Director API to verify the user privileges on a set of entities or the user granted privileges, the API returns a reduced or an empty set of rights for this user.

  • Running an API to query a multisite deployment might return inconsistent results

    Running any API to query a multisite deployment might return results with missing or duplicate entries on pages after the first one.

  • You cannot launch the web console for a VM

    If your vSphere environment uses a different than the standard 443 network port for the VM console communication, when you attempt to launch the VM web console, the resulting new browser tab is blank.

  • LDAP users are randomly disappearing from VMware Cloud Director

    If your VMware Cloud Director environment contains LDAP configured with more than 250 users and some of the users belong to a custom Active Directory organizational units, after performing an LDAP synchronization, the system marks the users as stranded and they disappear from VMware Cloud Director.

  • Users cannot log in to some organizations after migration to or from the system organization LDAP configuration

    If you migrate a user from the shared system organization LDAP configuration to another IDP source, and the reverse, that user cannot log in to any organization other than the one doing the migration. For example, in a deployment where the system organization manages TenantA and TenantB and all organizations import User1 from the shared system organization LDAP configuration, if TenantA sets up a SAML configuration and migrates User1 from LDAP to SAML, then, User1 can log in to TenantA through SAML, but they cannot log in to the system organization or TenantB.

  • Deleting auto-discovered VMs from VMware Cloud Director moves the existing VMs in vApps to the StrandedItems folder and renames them

    When you delete the auto-discovered VMs from VMware Cloud Director, the system moves the existing VMs that reside in vApps to the StrandedItems folder in vCenter Server and renames the VMs with a suffix, similar to vcentervm-1 (vm-uuid).

  • Creating a vApp from an OVF fails with a Computer name cannot be longer than 15 characters error message

    When you create a new vApp from an OVF package, if the OVF contains multiple vmx-XX strings under the VirtualSystemType entry, the creation fails with an error message.

    Computer name cannot be longer than 15 characters

  • Creation of a new VM fails with a Reconfiguration of vmGroups: timed out for cluster error message

    If an organization VDC has a placement policy as the default compute policy and only one VM sizing policy, when you deploy a new VM or a vApp without selecting the placement policy, instead of applying the default placement policy, VMware Cloud Director applies the VM sizing policy. This might cause the operation to fail with an error message.

    Reconfiguration of vmGroups: timed out for cluster

  • The drop-down menu for custom set of segment profiles does not display the segment profiles

    When configuring a segment profile of organization VDC networks that is backed by NSX, the drop-down menu does not display the custom segment profiles.

  • An attempt to delete a virtual service changes the status of the service to REALIZATION_FAILED

    For an edge gateway load balancer, when you attempt to create multiple virtual services concurrently, some of the virtual services display a Critical status. Attempting to delete these virtual services changes their status to REALIZATION_FAILED.

  • Мigration from NSX Data Center for vSphere to NSX-T Data Center fails

    When configuring an external network, if you do not configure at least one IP address in the static IP pool, an attempt to migrate from NSX Data Center for vSphere to NSX-T Data Center fails during the prepareTargetVDC phase of the operation with an error message.

    line 419, in createOrgVDCNetwork KeyError: 'subnets'

  • Registering a second NSX Cloud instance fails with a Cannot register Load Balancer Cloud since another Load Balancer Cloud <cloud> is already associated error message

    If you define the same network pool backed by an NSX transport zone for two or more NSX Cloud instances and you register one of the NSX Cloud instances with VMware Cloud Director, registering the second instance fails with an error message.

    Cannot register Load Balancer Cloud <cloud> since another Load Balancer Cloud <cloud> is already associated

  • An attempt to view a vApp results in a class java.net.Inet6Address cannot be cast to class java.net.Inet4Address error message

    In a vApp, if you add a direct vApp network that is linked to a routed organization VDC network containing both IPv4 and IPv6 DNS addresses, an attempt to view the vApp results in a class java.net.Inet6Address cannot be cast to class java.net.Inet4Address error message.

  • Configuring and updating the IPsec VPN and L2 VPN tunnels fail with a Cannot create or update VPN Tunnel error message

    When you attempt to configure a new or update an existing IPsec VPN or L2 VPN tunnel, the operation fails with an error message.

    Cannot create or update IPSec VPN Tunnel

    Cannot create or update L2 VPN Tunnel

Known Issues

  • New - 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.

  • New - 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.

    Workaround:

    • Log in to VMware Cloud Director with a tenant account.

    • Alternatively, you can deactivate the monitoring that ends VM console sessions for deactivated users. If you deactivate the monitoring, VMware Cloud Director will not end VM console sessions of deactivated users.

      1. Log in directly or by using an SSH client to the OS of a VMware Cloud Director cell as root.

      2. Change the default value of the configuration settings.

        cd /opt/vmware/vcloud-director/bin
./cell-management-tool manage-config -n console-proxy.monitor-interval-ms -v 9223372036854775807

      3. To verify the current value, run the following command.

        ./cell-management-tool manage-config -n console-proxy.monitor-interval-ms -l

    See KB article 95214.

  • New - 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.

  • New - 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.

  • You cannot create VMware Cloud Director VDC templates in VMware Cloud Director service environments

    VMware Cloud Director service does not support Virtual Data Center (VDC) templates. You can use VDC templates on environments with provider VDCs with an NSX network provider type or an NSX Data Center for vSphere provider type. You cannot use VDC templates on VMware Cloud Director service environments because the provider VDCs have the VMC network provider type.

    Workaround: None.

  • 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 a VDC template and instantiate a VDC from a template if you are using only a VMware Cloud on AWS network pool for your provider VDC

    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.

    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