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

Products

• VMware Tanzu Application Service
• Operations Manager

Issue/Introduction

When running Apply changes against any tile on TPCF, it fails with "No valid placement found for VM compute and storage requirement" as below - 

L Error: CPI error 'Bosh::Clouds::CloudError' with message 'No valid placement found for VM compute and storage requirement' in 'create_vm' CPI method (CPI request ID: 'cpi-156849')

 

Environment

VMware Tanzu Elastic Application Runtime

Operations Manager

Cause

Kindly follow below steps to investigate. 

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

Step 2. Investigate the cpi output for the exact error message. As an example:

D, [2026-03-03T06:29:40.414026 #15878] DEBUG -- [req_id cpi-156849]: Failed to find placement for Disk ==> Disk CID: Size:262144 Ephemeral:true Target-DS:^(example)$ Existing-DS:
E, [2026-03-03T06:29:40.414459 #15878] ERROR -- [req_id cpi-156849]: Error in creating vm: No valid placement found for VM compute and storage requirement, Backtrace - /var/vcap/data/packages/vsphere_cpi/b6fbe6346ef7d80c6b4f3552a74399d3e9a41d83/lib/cloud/vsphere/vm_config.rb:254:in `cluster_placement_internal'

 

Resolution

The error message indicates the issue is with underlying DS. 

First, check the Target-DS on vSphere for the capacity usage. If the DS is full, please contact your 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.

Also check the hosts' capacity in vCenter.  If the hosts do not have enough free CPU or RAM to allocate, then the error will be encountered.

If you still face the issue after checking the above, please raise a case with Broadcom support, and include the CPI logs for review.