Partner integration between the cluster and harbor CN not working

Products

• VMware Telco Cloud Automation

Issue/Introduction

During instantiation, CNF Operations, can choose Cloud from the menu, but cannot view/select Repository URL(s) . The option gets disabled.

The Harbor connection status will be in Initiated state as shown in below snippet

TCA API logs:

2026-03-02T14:55:48.923434184Z stdout F 2026-03-02 14:55:48.923 UTC [vimstats-update-pool3, , , TxId: ] WARN  c.v.vca.hybridity.util.NSPRestClient- Login to cloud https://[email protected] failed, with status 401: Unauthorized 
2026-03-02T14:55:48.923580051Z stdout F 2026-03-02 14:55:48.923 UTC [vimstats-update-pool3, , , TxId: ] WARN  c.v.vca.hybridity.util.NSPRestClient- Invalid credentials logging into remote endpoint: https://[email protected], userName: test-cluster 
2026-03-02T14:55:48.923590167Z stdout F 2026-03-02 14:55:48.923 UTC [vimstats-update-pool3, , , TxId: ] WARN  c.v.vca.hybridity.util.NSPRestClient- Login failure to xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
2026-03-02T14:55:48.923655661Z stdout F 2026-03-02 14:55:48.923 UTC [vimstats-update-pool3, , , TxId: ] ERROR com.vmware.hybridity.nfvm.VnfUtils- Failed to query the TCA-CP Api GET:/hybridity/api/vimstats?nextpage_opaque_marker=page_no=1,page_size=50. 
2026-03-02T14:55:48.92366169Z stdout F java.lang.RuntimeException: Invalid credentials

Environment

2.3 or 3.x

Cause

Starting from TCA 2.3, TCA supports automatic certificate renewal for both management cluster and v2 workload clusters.

In certain cases, the certificates are renewed, but these are not synced to the TCA appliances. In such cases, it is required to manually update the Cluster certificates and / or kubeconfig stored in TCA database.

Resolution

Apply KB: Manually synchronize renewed CaaS kubeconfig for VMware Telco Cloud Automation