Management cluster deployment fails during tanzu context use

Products

• VMware Telco Cloud Automation
• VMware Telco Cloud Platform

Issue/Introduction

• In TCA 3.2.0, attempts to deploy a 1.28.11 management cluster may fail even though all control plane and worker node virtual machines are successfully created.
• The deployment times out in the TCA user interface and fails to complete. Log analysis reveals the failure occurs when the Tanzu CLI tries to execute the tanzu context use command.
• This issue can block production deployments and CNF onboarding workflows.

Environment

• TCA: 3.2.0

• TCP: 5.0

• Management cluster version: 1.28.11

• Air-gapped deployment

 

Cause

The failure is caused by missing or malformed configuration entries in the following files inside the kbs-tkg252 pod:

/root/.config/tanzu/config.yaml
/root/.config/tanzu/config-ng.yaml

Specifically, the required server and context definitions for the new management cluster are absent. As a result, the Tanzu CLI fails to retrieve the necessary credentials to proceed with the deployment.

Resolution

1. Open a shell in the pod:

   kubectl exec -n <namespace> <pod-name> -it bash

2. Edit the file at /root/.config/tanzu/config.yaml and add the following content, replacing <cluster-name> with your actual cluster name:

   servers: - name: <cluster-name> type: managementcluster managementClusterOpts: path: /root/.kube-tkg/config context: <cluster-name>-admin@<cluster-name> current: <cluster-name>

3. Edit the file at /root/.config/tanzu/config-ng.yaml with the corresponding context block:

   contexts: - name: <cluster-name> target: kubernetes clusterOpts: path: /root/.kube-tkg/config context: <cluster-name>-admin@<cluster-name> isManagementCluster: true contextType: kubernetes discoverySources: [] currentContext: kubernetes: <cluster-name>

4. Run the following command to validate:

   tanzu context use <cluster-name>

5. Retry the management cluster deployment through the TCA user interface.