Table 2. Known issues in product version
Issue ID | Functional area | Description | Workaround/solution |
DTVMWARE-144 | Telco Cloud Automation (TCA) | The Tanzu Kubernetes Grid (TKG) cluster has an expired certificate. Operations such as cluster creation, node pool creation, and node customizations will fail. | See the VMware KB article 85643: Recovering TCA from NodeConfig-Operator Webhook Service Certificate Expiration. |
DTVMWARE-146 | TCA | Redeploying harbor through TCA results in a “Namespace already exists” error. | Secure Shell (SSH) to the master node IP and run {{kubectl delete namespace harbor. T}}. Restart the job. |
DTVMWARE-179 | TCA | If the Management and Workload clusters are upgraded to 7.0.2, deploying the Compute cluster installed with ESXi_7.0.2 fails. | Deploy the Management, Workload, and Compute cluster using ESXi 7.0.1, and then upgrade the cluster to ESXi_7.0.2. |
DTVMWARE-180 | TCA | TCA has limitations in creating single disk groups per host. If any host in the cluster has extra SSD disks and HDD disks that are not used on a disk group, they will not be used during deployment. Attempting to re-synchronize the deployment of such a domain or site will fail. |
For hybrid disk groups, each host contributing storage must contribute one flash cache device and one or more HDD capacity devices. Only one cache device can be added per disk group.
For all-flash disk groups, each host contributing storage must contribute one flash cache device and one or more flash capacity devices. Only one cache device can be added per disk group.
|
DTVMWARE-184 | TCA | Workload deployment fails at 90 percent: Migrate management VM’s in workload domain to management domain. | Resync the Workload domain. After the resync, the Workload domain deployment completes successfully. |
Issue ID | Functional area | Description | Workaround/solution |
DTVMWARE-198 | TCA | CA 1.9.5 fails to deploy NDC with Toshiba HDD. The drive type is Toshiba HDD. Cloud Builder assumes it is an SSD drive and fails vSAN readiness. | Replace the drive with a Seagate HDD. |
DTVMWARE-199 | TCA | TCA 1.9.5 takes more than 24 hours to error out while deploying a Compute Cluster site when there is a configuration issue of any kind. |
|
DTVMWARE-200 | TCA | TCA 1.9.5 does not get an alarm if vSwitches are missing a virtual-machine network interface card (vmnic). | Add the vmnic to the TCA UI / switches section and resync. To be fixed in TCA 2.0. |
DTVMWARE-203 | TCA | TCA 1.9.5 is unable to get the harbor connected. | Perform a force sync and restart services (see VMware internal tracking PR 2834956). |
DTVMWARE-206 | TCA | After deploying a Management Domain Central Site (NDC) or a Workload Domain site (WLD), TCA 1.9.5 may fail to remove the datastore created for Cloud Builder. | Remove the datastore manually. |
DTVMWARE-202 | Upgrade | During ESXiU1 to ESXiU2, when manage is used with a single image, the following pre-check error is displayed when you attempti to convert to an image: “Transport Node Profile is not configured on the cluster but NSX-T Data Center is installed on the following host(s): ESXi10, ESXi11, ESXi12, ESXi13.” | Enabling vLCM is not allowed if cluster members are Transport Nodes (with NSX VIBs installed) and there is no Transport Node Profile (TNP) attached. Select the Cluster checkbox and click the Configure NSX menu. In the next popup, select TNP. |
DTVMWARE-204 | Upgrade | ESXi7U1 to ESXi7U2 with Life Cycle Manager (LCM) remediation is triggered at the cluster level, putting the host in maintenance mode indefinitely. | Manually take the hosts out of maintenance mode (see VMware internal tracking PR2825198). |
DTVMWARE-185 | vRLI | vRLI doe not have NSXT version 3.0.2 content pack. | Find the correct content pack for vRLI from the VMware site and import it to vRLI. If there are still logs missing, reboot vRLI VM. |
DTVMWARE-177 | vSAN | vSAN Cluster issues lead to a “Performance service is disabled” warning on the Compute cluster. |
|
DTVMWARE-144 | Telco Cloud Automation (TCA) | The Tanzu Kubernetes Grid (TKG) cluster has an expired certificate. Operations such as cluster creation, node pool creation, and node customizations will fail. | See the VMware KB article 85643: Recovering TCA from NodeConfig-Operator Webhook Service Certificate Expiration. |