Cluster creation stuck in provisioning status

Products

• VMware Telco Cloud Automation

Issue/Introduction

• When deploying a cluster or nodepool with a name that was used before in the environment at some point, you will see the cluster is provisioning state
• Checking the nodes on the nodepool from the TCA Manager Cli by running kubectl get nodes -o wide you might see them in:
  

  Ready,SchedulingDisabled

• The customization of the nodes can also be stuck in provisioning  

Environment

3.2.0.1

Resolution

Apply the Patch Tool for TCA 3.2.0.1 KB.