Error: Invalid value: "nodeprofile": kernelMods merge failed: must specify source for module dpdk

Products

• VMware Telco Cloud Automation

Issue/Introduction

• Node pools in a workload cluster may show “processing” with error.
  
  
• Clicking on the error message, you will see this:
  • Failed to apply NodePolicy CR. Cluster: Cluster-Name, Operation: Customize, Intent: ########-####-####-####-############, NodePool: Node-Pool-Name, Details: HttpStatus: 403 : admission webhook "validator.vmconfig.acm.vmware.com" denied the request: NodePolicy.acm.vmware.com "Node-Pool-Name" is invalid: [spec.kernelMods: Invalid value: []v1alpha1.KernelModSpec{v1alpha1.KernelModSpec{Name:"dpdk", Version:"21.11", Source:""}}: must specify source and version for module dpdk, spec.nodeconfig: Invalid value: "nodeprofile": kernelMods merge failed: must specify source for module dpdk]

 

• From the Mgmt Cluster:
  
  kubectl logs -n tca-system vmconfig-operator-##########-#####

• • 2024-12-03T15:00:23.328Z        INFO    nodepolicy-resource     failed to pass nodeconfig validation    {"error": "kernelMods merge failed: must specify source for module dpdk", "cr": "node-pool-name"}
    2024-12-03T15:00:23.328Z        DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/validate-acm-vmware-com-v1alpha1-nodepolicy", "UID": "########-####-####-####-############", "allowed": false, "result": {}, "resultError": "got runtime.Object without object metadata: &Status{ListMeta:ListMeta{SelfLink:,ResourceVersion:,Continue:,RemainingItemCount:nil,},Status:,Message:,Reason:NodePolicy.acm.vmware.com \"node-pool-name\" is invalid: [spec.kernelMods: Invalid value: []v1alpha1.KernelModSpec{v1alpha1.KernelModSpec{Name:\"dpdk\", Version:\"21.11\", Source:\"\"}}: must specify source and version for module dpdk, spec.nodeconfig: Invalid value: \"nodeprofile\": kernelMods merge failed: must specify source for module dpdk],Details:nil,Code:403,}"}

Environment

2.3

Resolution

Workaround:

The node pool needs to be created again.

Fix:

Resolved in TCA 3.1.