'VirtualMachineServices LB doesn`t get VIP assigned: VirtualMachineServices LB does not any ingress'

Products

• vSphere with Tanzu

Issue/Introduction

^{After changing the NSX Manager password, the NCP pods failed to authenticate.}

Environment

^{vSphere with Tanzu}

Cause

^{The NSX Manager password was changed, and reauthentication with the vCenter Server was not performed. The NCP pod logs indicate the same.} 

 

^{[ncp MainThread W] vmware_nsxlib.v3.cluster Request failed due to: The credentials were incorrect or the account specified has been locked.}

^{[ncp MainThread W] vmware_nsxlib.v3.cluster Request failed due to an exception that calls for regeneration. Re-generating pool.} 

^{[ncp MainThread I] nsx_ujo.ncp.vc.session Refreshing token and re-instantiating TESSession}

^{[ncp MainThread I] nsx_ujo.ncp.vc.session VC credentials were not changed}

^{[ncp MainThread I] nsx_ujo.ncp.vc.session Successfully retrieved JWT token}

Resolution

^{Part A:} 

^{Navigate to NSX Manager:}

^{System -> Fabric -> Compute Manager -> Edit -> Disable trust -> Save, and then re-enable it.} 

^{Part B:} 

• ^{Establish a PuTTY session to the vCenter Server.}
• ^{Run the following command:}

^{/usr/lib/vmware-wcp/decryptK8Pwd.py}

• ^{Note the IP address and password provided.}

• ^{SSH into the Supervisor Cluster using the IP address obtained.}

• ^{Run the following command to check the NCP deployments} 

kubectl get deployments -A | grep -i ncp  

• ^{Restart the NCP deployment using:}

kubectl rollout restart deployment -n <deployment namespace> <ncp-pod-deployment-name>