CNF deployment failed during instantion
search cancel

CNF deployment failed during instantion

book

Article ID: 390846

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

CNF re-deployment failed issue is observed with the below errors:

kubectl -n cnf-01 describe pod test-pod-aa-mobility-#######-####Events:
  Type     Reason            Age                   From               Message
  ----     ------            ----                  ----               -------
  Warning  FailedScheduling  28m (x59 over 5h10m)  default-scheduler  0/66 nodes are available: 3 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 57 Insufficient cpu, 6 node(s) didn't match Pod's node affinity/selector. preemption: 0/66 nodes are available: 57 No preemption victims found for incoming pod, 9 Preemption is not helpful for scheduling..

Environment

2.x, 3.x

Resolution

Please contact the application vendor to review the application requirement as listed in the reported error.