No valid placement found for VM compute and storage requirement while running apply changes

Products

• VMware Tanzu Application Service
• VMware Tanzu Application Service
• VMware Tanzu Application Service for VMs

Issue/Introduction

Customer added extra headers' in the isolation-segment-uat Zone / Networking tab and reviewed Pending Changes -

Then, Apply Changes failed during deploy the ISO segment and errored out "No valid placement found for VM compute and storage requirement" as below - 

 

Resolution

Kindly follow below steps to investigate. 

Step 1. Run command "bosh task <task-id> --cpi" to get the bosh CPI log, the output as below --

D, [2024-10-09T08:28:40.955612 #2950996] DEBUG -- [req_id cpi-351047]: Failed to find placement for Disk ==> Disk CID: Size:81920 Ephemeral:true Target-DS:^(###03_2n_00_7a07|###03_2n_16_7a08|###03_2n_17_7a09|###03_2n_18_7a0a)$ Existing-DS:
E, [2024-10-09T08:28:40.955722 #2950996] ERROR -- [req_id cpi-351047]: Error in creating vm: No valid placement found for VM compute and storage requirement, Backtrace - /var/vcap/data/packages/vsphere_cpi/338faab00384182e4f60a62e66e784b853d31d69/lib/cloud/vsphere/vm_config.rb:233:in `cluster_placement_internal'

The error message "Failed to find placement for Disk ==> Disk CID: Size:81920 Ephemeral:true Target-DS:^(###03_2n_00_7a07|###03_2n_16_7a08|###03_2n_17_7a09|###03_2n_18_7a0a)$ Existing-DS:" indicates the issue is with underlying DS. 

Step 2. Further checking from the vSphere console, we can see the capacity and usage of DS is low. For example,###03_2n_00_7a07 only has 20.5 GB free.

Step 3. Suggest the customer to contact their Infra Team to increase the storage and have a try again.

---

If this problem occurred when making change to datastore configuration (when making changes to migrate datastore), then please also ensure:

• Ensure that clusters configured in OpsManager > BOSH Tile > Availability Zones have access to datastores configured in vCenter Config >  Ephemeral Datastore Names and Persistent Datastore Names
• If configured clusters do not have access to Datastore, then you will need to Add Cluster to Availability Zones to rectify this mismatch.
• After adding clusters with proper datastore access, apply changes should now run without getting placement errors.