Error: "Failed to apply NodePolicy CR. Cluster: xxx-xx-xxxxxxxxxxxx-sh-2, Operation: Customize, Intent: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx, NodePool: np1, Details: {4}" during workload creation failure.
search cancel

Error: "Failed to apply NodePolicy CR. Cluster: xxx-xx-xxxxxxxxxxxx-sh-2, Operation: Customize, Intent: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx, NodePool: np1, Details: {4}" during workload creation failure.

book

Article ID: 422456

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

  • Workload cluster creation keeps failing.
  • After creating a workload cluster, the node pool status does not become provisioned and we see the following error is shown in the Node Pools section.

Failed to apply NodePolicy CR. Cluster: xxx-xx-xxxxxxxxxxxx-sh-2, Operation: Customize, Intent: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx, NodePool: np1, Details: {4}

  • Log snippets :  

 /var/log/kafka-connect and look out for “CreateKafkaPipeline


2025-12-09 05:35:14.901 UTC [NfvmService_SvcThread-41, Ent: DEFAULT, Usr: [email protected], , TxId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx] INFO  c.v.h.nfvm.CreateKafkaPipelineJob- Starting to Run Job CreateKafkaPipeline with Job Id xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx State: WAIT_FOR_KAFKA_PIPELINE

  • The connection with TCA-CP is degraded and does not become OK.
  • Validated under TCA manager UI, the status showed degraded and there were no DNS changes made.
  • The issue existed since the time it was deployed.

Environment

  • VMware Telco Cloud Automation 3.x

Cause

  • In the TCA CP, the  "externalAddress" is incorrect or set to same as TCA-M "externalAddress"
  • Reconfiguring TCA-CP to have the correct "externalAddress" would help in fixing the problem.

Resolution

  • Steps to fix the "externalAddress" typo.


1. SSH into TCA CP as admin

2. Retrieve the tcxproduct using kubectl

#kubectl get tcxproduct -A

3. Save the TCA-mgr to a YAML file

#kubectl get tcxproduct tca-mgr -n default -o yaml  > tca-mgr-tcxproduct.yaml 

4. Edit the kafka-strimzi value for helmOverride

5. Decode the base64 value

6. Update the value "dev-tb-xxxxxxm0001x.xxx.home" to "dev-tb-xxxxxc0001v.xxx.home"

7. Encode the tcxproduct with update hostname from step #6

8. Update the encoded value to tcxproduct yaml.

9. Repeat the same procedure for tca Helm Chart

10. Once done, apply the new configuration YAML with "kubectl apply"

11. Reboot the appliance.