TCA node pool reconfigure operation stuck in processing status

Products

• VMware Telco Cloud Automation

Issue/Introduction

• When attempting to update the CPU and memory allocation of an existing node pool, the node pool becomes unresponsive and remains stuck in a queued status.
• Subsequent deletion attempts fail while the node pool remains in this processing state.

Environment

TCP 5
TCA 3.4

Cause

Underlying cluster resource constraints prevent the vmconfig-operator from reconciling the new node pool configuration, causing the operation to hang in a queued state.

Resolution

To delete the stuck node pool, reduce the resources allocated to it, and then attempt the deletion operation again.If the node pool remains stuck after reducing resources:

1. Verify the health of the vmconfig-operator pod on the TKG management cluster.
2. Attempt a non-destructive dummy node pool operation (e.g., a small metadata change) without modifying core CPU/Memory/Network configurations to force a reconciliation trigger.
3. If pods show "ImagePullBackOff" or certificate errors, investigate management pod failures.
4. Node pool deletion or reconfiguration operations may become stuck or fail for a variety of reasons. If deletion through the UI or CLI continues to fail and stale entries require manual TCA database cleanup, open a support case for further assistance.