Node pool Deployment stuck in processing state with the error of vmconfig.spec.revision is not matched

Products

• VMware Telco Cloud Automation

Issue/Introduction

When adding a new node pool using Telco Cloud Automation, we see that the task never finishes and gets stuck in processing state. In the Node Pools section of the CaaS Infrastructure we see this error and the reason for the Nodepolicy Ready is showing error "

reason: >-vmconfig.spec.revision is 1736929043, nodeprofilestatus.revision is 1736922075.nodeConfig.revision 1736922075 is not same as nodepolicy.spec.revision 1736929043 and is stuck in configuring status with error " 

reason: >-Normal/Configuring/Failed/Total: 0/1/0/1.nodes [nodename-abc/NodeConfigRev/1736922075] revision is not matched.

Environment

2.3

Resolution

Restart the vmconfig opearator pod on the TKG Mgmt Cluster

kubectl rollout restart deploy/vmconfig-operator -n tca-system