VMware : Error no matching placement in VMware Aria Automation 8.18.1

If you are using VMware Aria Automation and encounter the error:  “No matching placement. Error: No storage profiles are matching the disk requirements”, this guide will help you resolve the issue.

After updating VMware Aria automation to version 8.18.1, we reported this error when provisioning VMs for some cloud zones.

The primary cause is an inconsistency in storage profiles, but when we try to add a datastore to the storage profile, the operation turns into a timeout

The first step is identifying the storage profile ID, which can be easily identified with the URL.

SSH to Aria Automation appliance and Run the following command to open the provisioning database:

#vracli dev psql

Connect to the provisioning database

template1=# \c provisioning-db;

Enable expanded mode. The results are displayed as a vertical list, which is helpful when the rows contain many columns and the table becomes challenging to read.

provisioning-db=# \x

Check the storage profile association state. Replace STORAGE PROFILE ID with the actual ID of your storage profile:

provisioning-db=# select * from storage_profile_association_state where storage_item_id=STORAGE PROFILE ID;

The storage profile is still referenced but marked as DELETE:

You can see in the storage profile description the name of the datastore

provisioning-db=# select * from storage_description where document_self_link = ‘/resources/storage-descriptions/ID‘;

you can manually remove it using:

provisioning-db=# DELETE from storage_profile_association_state where storage_item_id= STORAGE PROFILE ID ‘;

Broadcom has acknowledged this issue and is working on a fix. A patch will be included in the upcoming 9.0 release of VMware Aria Automation.

Enjoy!