How to troubleshoot cluster creation issues for clusters created with Tanzu Mission Control

Products

• Tanzu Mission Control

Issue/Introduction

This article highlights some troubleshooting steps that you can use when you create a new cluster with TMC that is stuck in Creating state

Symptoms:

You use Tanzu Mission Control (TMC) to create a new cluster and even after a few hours you see the status hasn't changed. The status is stuck in a Creating state.

Cause

When a cluster creation fails, TMC will retry the cluster creation indefinitely. Therefore, it will continue to retry creating a cluster until you provide a resolution to the underlying problem causing the cluster creation failure. 

Resolution

Consider the following when troubleshooting what is causing the new cluster to be stuck.

• Check if sufficient resources are available or not for provisioning a cluster. Please check with your IaaS. Check with your IaaS Monitoring tool to see if there are any alarms with regards to resources such as memory, disk, etc. 
• Check the status of the management cluster and check if any of the pods under the vmware-system-tmc namespace are not running with the following command:

kubectl get pods -n vmware-system-tmc

• If any of the pods are not in a running state under vmware-system-tmc, get the logs with the command below. 

kubectl logs -n vmware-system-tmc lcm-tkg-extension-<xxxx>

Note: Get the logs of the extension by putting in the pod name obtained when checking if any of the pods under the vmware-system-tmc namespace are not running.

Additional Information

For more information on how to provision a cluster refer to the Provisioning Tanzu Kubernetes Grid Workload Clusters section in the TMC documentation.