"Unable to reach tca service from ingress. Please check the status of the service by accessing the cluster" while launching the TCA-CP UI Page

Products

• VMware Telco Cloud Automation

Issue/Introduction

Unable to access TCA control plane through UI.
Access through SSH and CLI operations are successful.
tca-api -xx-xx POD is in crashloopBackoff status

 

 

Environment

TCA 3.x

Cause

The tca-api -xx-xx POD is in crashloopBackoff status.  

Logs indicate that the pod is unable to state due to authentication failure with the vCenter Server 

2025-09-05 01:00:40.019 UTC [http-nio-8443-exec-6, , , TxId: ] INFO  c.v.vchs.hybridity.audit.AuditTrail- {"internal":{"threadEnterprise":"No Thread Context","threadUser":"No Thread Context","thread":"http-nio-8443-exec-6","lineNumber":165,"classname":"com.vmware.vchs.hybridity.api.LoginUtil","method":"logAuth"},"userIdentities":[{"username":"[email protected]","tenantId":"default","enterprise":"DEFAULT","organization":"DEFAULT","userRoles":[],"endpointId":"2xxx"}],"tenantIds":["default"],"severity":"CRITICAL","userIdentity":{"username":"[email protected] "},"eventId":"######-#####-#########","eventTime":######,"message":"Access Denied","eventName":"Login Failed","service":{"name":"Login Failed"},"restEndpoint":{"uri":"\/tca\/global\/api\/v1\/sessions",
"method":"POST","sourceIPAddress":"10.10.x.x"},"requestParameters":{"query":[]},"responseElements":{"isAuthenticated":"false"}}
2025-09-05 01:00:40.025 UTC [http-nio-8443-exec-6, , , TxId: ] ERROR c.v.v.h.a.HybridityAccessDeniedHandlerImpl- Sending Response Error 403 for /tca/global/api/v1/sessions
2025-09-05 01:00:40.053 UTC [http-nio-8443-exec-3, , , TxId: ] WARN  c.v.t.w.s.TcaSecurityAnnotationEvaluator- Access denied to logout authentication is required
2025-09-05 01:01:02.067 UTC [Timer-0, , , TxId: ] INFO  c.v.v.h.a.SessionPurgingMapSessionRepository- Started Purging session. Current Map count 0
2025-09-05 01:01:52.156 UTC [http-nio-8443-exec-8, , , TxId: ] INFO  c.v.t.d.AuthenticationServiceByVc- Admin service config:

This issue occurs when the kublet certificate was not rotated successfully after renewing the vCenter certificate renewal.

 

Resolution

Rotate the kubelet certificate using the script provided in https://knowledge.broadcom.com/external/article?articleNumber=382787