After upgrading the TCA-CP appliance from version 3.3 to 3.4, the TCA-CP UI on port 9443 fails to launch

Products

• VMware Telco Cloud Automation
• VMware Telco Cloud Platform

Issue/Introduction

• Post TCA-CP upgrade to 5.1 the UI status shows as successful:
  
• After the reboot of the appliance from the tca-cp console the system pods status shows Error | Pending:
  
• TCA-CP is connected to two TCA-M which is not supported. (Or at least it was re-assigned from one TCA-M to another and some garbage left in the database)
  

  tca=# SELECT id, val->'source'->>'uuid' as tca_m_uuid, "destinationUrl", "destinationUuid", "creationDate", "lastUpdated", "sourceUuid" FROM "endpointLink" WHERE "type" = 'HYBRIDMANAGER_PAIRED';
  
   id |                       tca_m_uuid                       |               destinationUrl                |                    destinationUuid                     |        creationDate        |        lastUpdated         |                       sourceUuid                       
  
  ----+--------------------------------------------------------+---------------------------------------------+--------------------------------------------------------+----------------------------+----------------------------+--------------------------------------------------------
   47 | 2yyyyyyyy-xxxxxx-xxxx-xxxxxxxxxxx | https://tca-cpxxxxx.com | 2yyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx | 2024-05-02 09:41:05.011638 | 2024-05-07 07:09:29.252849 | 2yyyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx
  
   52 | 2yyyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx | https://tca-cpxxxxx.com | 2yyyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx | 2024-05-07 08:31:10.201297 | 2025-09-18 11:24:03.397378 | 2yyyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx
  
  (2 rows)

Environment

TCP 5

Cause

In TCA 3.4 new pairing feature introduced which needs exactly one TCA-M per TCA-CP.

Resolution

1. Delete the stale record from the database before the upgrade. Check which is the alive TCA-M uuid.
2. Find the TCA-M uuid by executing the below steps from TCA-M
   1. ssh to tca manager appliance using the admin credentials
   2. execute the following command:
      

      kubectl exec -it postgres-0 -n tca-mgr -- psql -d tca -U tca_admin -h localhost

   3. 
      

      select * from "endpointLink" where val->>'isSelf' = 'true';

      Kindly ensure that you roll back TCAP-CP upgrade using the Snapshot of tca-cp appliance to last known good status and then perform the following steps:
      Note down the TCA-M uuid and compare it with the above out put. we need to delete the other stale entry.
      Example:
      
      Active TCA-M : 2yyyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx1e26801a3570 
      Stale TCA-M: 2yyyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx76df34c67d47

3. Delete the stale TCA-M stale entry from TCA-CP. 
   

   Delete from "endpointLink" where id in (select id from "endpointLink" where val::TEXT LIKE '%2yyyyyyyy--xxxxxx-xxxx-xxxxxxxxxxx76df34c67d47%');

4. Exit from DB: 
   

   exit

5. Reboot the TCA-CP appliance and then perform the TCA-CP Upgrade from UI
   
   Refer the following document which has the detailed procedure to  upgrade TCA-CP Appliance Upgrade VMware Telco Cloud Automation Using the Upgrade Bundle

Additional Information

Refer the following document which has the detailed procedure to  upgrade TCA-CP Appliance