Nodepolicy stuck in Configuring/Failed state

Products

• VMware Telco Cloud Automation

Issue/Introduction

• Nodepolicy stuck in Configuring or Failed when checking by running the command:
  

  kubectl get nodepolicy -A

• Describing the nodepolicy showing as failed says 
  

  nodeconfig status is failed

• When attempting a dummy edit on Nodepools, the operation fails with:
  

  JSON parse error: Unrecognized field :nameserversStr

• The node that is part of the nodepolicy will show in SchedulingDisabled and the node VM will not power on, on it own
• The Connected Endpoints Certificate is displayed as Expired in the TCA Manager for the TCA-CP

 

Environment

3.2

Cause

• The issue is caused by an expired Connected Endpoints Certificate
• When the certificate expires, secure communication between TCA components (Manager, Control Plane, and Endpoints) fails

Resolution

To resolve this issue, the expired Connected Endpoints Certificate must be renewed.

1. Log in to the TCA Manager UI.

2. Navigate to Connected Endpoints.

3. Identify the endpoint with the expired certificate.

4. For TCA-CP cert renewal you can follow the official Tech Document Update Server Certificate

5. Once the certificate status shows "Connected" retry the Nodepool operation (the dummy edit that previously failed).