"Error: 'Internal server error' during kubectl login due to WCP service resource leak in vCenter 8.0U3g".

Products

• Tanzu Kubernetes Runtime
• VMware vCenter Server

Issue/Introduction

Cannot log into guest clusters after auth certificates are replaced using Cannot login to vSphere with Tanzu TKC guest cluster after renewing vCenter machine certificates with error 

Receive following error when trying to log into a guest cluster using kubectl vsphere login:
FATA[2026-00-00 00:00:00.000] Error while connecting to host <IP_ADDRESS>: internal server error.


From the /var/log/vmware/wcpsvc.log you will see the follow error:

debug wcp [kubelib/auth.go:192] [opID=6a3a8459-1d31220c-c273-4c7e-bdd0-3fcb2f8c491b-848b] Auth roundtripper: retry request. Response statusCode: 401
debug wcp [kubelib/auth.go:192] [opID=6a3b33b2-a02c] Auth roundtripper: retry request. Response statusCode: 401

Environment

vCenter Server 8.0 Update 3g, 8.0.3.00600

Cause

Memory leak in the WCP service on vCenter not allowing login to vSphere with Tanzu TKC guest cluster.

Resolution

The memory leak issue was fixed in 9.1. On 8.x branch is fixed in 8.0 P10.

A workaround is to reboot the wcp service on the vCenter:

• Log into vCenter SSH
• Run service-control --restart wcp
• After check the service is up service-control --status --all