The issue only occurs on platform with NSX network. During VM deployment or recreation, below error is returned and the newly created VM can not be associated with the specified IP by BOSH.
Task 20765 | 11:01:26 | Preparing deployment: Preparing deployment (00:00:01)
Task 20765 | 11:01:27 | Preparing deployment: Rendering templates (00:00:01)
Task 20765 | 11:01:29 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 20765 | 11:01:29 | Creating missing vms: test_vm/#### (0) (00:10:34)
L Error: Unknown CPI error 'Unknown' with message 'Error while getting group associations from enforcement point : NOT_FOUND: Group association resource ID was not found.' in 'delete_vm' CPI method (CPI request ID: 'cpi-489477')
Task 20765 | 11:12:03 | Error: Unknown CPI error 'Unknown' with message 'Error while getting group associations from enforcement point : NOT_FOUND: Group association resource ID was not found.' in 'delete_vm' CPI method (CPI request ID: 'cpi-489477')
Task 20765 Started Wed Jan 14 11:01:26 UTC 2026
Task 20765 Finished Wed Jan 14 11:12:03 UTC 2026
Task 20765 Duration 00:10:37
Task 20765 error
When creating a VM, BOSH reaches out to NSX Manager to allocate and assign a specified IP to a segment port. The segment port is successfully created for the VM, but for NSX internal reason, the IP fails to be allocated and assigned to the segment port.
As the result, the newly created VM can not communicate with BOSH director due to missing IP address, BOSH director will start deleting the VM after waiting 600s. The deletion operation triggers error "Group association resource ID was not found", as the resource was not recreated on NSX and accordingly not available.
The problem is at NSX side, please engage your NSX Manager admin to review NSX Manager side event and log, figure out why the given IP can not be allocated and assigned to the proper segment port.