Recovery of TCA-CP after accidental deletion
search cancel

Recovery of TCA-CP after accidental deletion

book

Article ID: 438277

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

  • TCA Control Plane (TCA-CP) VM is missing from the vCenter inventory or has been permanently deleted.
  • TCA Manager UI displays associated Cloud Providers and Kubernetes clusters in a "Disconnected" or "Unknown" state.
  • Lifecycle Management (LCM) operations (e.g., node pool expansion, upgrades) fail for existing workload clusters.

Environment

2.3

Cause

In TCA 2.3, the TCA-CP maintains the "source of truth" for the regional CaaS layer within its local filesystem and PostgreSQL database (kbsctl). This includes the Management Cluster context, internal cluster UUID mappings, certificates, and SSH keys. Deletion of the appliance results in the permanent loss of this metadata. 

Resolution

If no file-level or image-level backups are available for the TCA-CP VM, a full reconstruction of the TCA management plane and CaaS layer is required to restore full orchestration capabilities.

  1. Decommission Orphaned Resources:
    • Remove the disconnected clusters and VIM entries from the current TCA Manager UI to prevent database conflicts.
  2. Redeploy Management Components:
    • Deploy a fresh TCA Manager OVA and integrate it with the vCenter SSO/Identity Provider.
    • Deploy a fresh TCA-CP OVA and register it to the new TCA Manager.
  3. Restore Cloud Integration:
      • Re-add the vCenter and NSX resources as Cloud Providers within the TCA Manager.
  4. Rebuild CaaS Layer:
      • Deploy a new Management Cluster via the new TCA-CP.
      • Deploy new Workload Clusters as required.
      • Migrate application manifests from the orphaned clusters to the new managed environment.
  5. Final Cleanup:
      • Once the new environment is validated, manually delete the orphaned Kubernetes VM folders from the vCenter inventory.

Note: While re-registering clusters as "Existing" provides visibility, it does not restore the ability to manage the underlying infrastructure. A clean rebuild is necessary to synchronize the TCA-CP database with deployed resources.

Powered by Wolken Software