Aria Automation deployment fails with "No placement exists that satisfies all of the request requirements"

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When attempting to provision a virtual machine using VMware Aria Automation, the deployment fails during the allocation phase. The deployment history shows an error similar to the following:

Original Task Error: 'Allocation filter error: Unable to find a common placement for compute 'Cloud_vSphere' and its associated network resources on region '(REGION-SDDCName)'. Reason: network filter: host does not conform with the network configuration based on the networks of the blueprint and the selected network profile 'KeyPair:Tag''

Environment

VMware Aria Automation 8.18.x

Cause

This issue typically occurs when there is a mismatch between the network configuration in Aria Automation and the actual underlying network infrastructure in the vCenter Server.

A common cause is a change made directly in vSphere that is not reflected in Aria Automation. For example, if a virtual machine port group was migrated from an NSX-backed Virtual Distributed Switch (N-VDS) to a standard vSphere Distributed Switch (VDS), Aria Automation's inventory would still be expecting the network to be on the N-VDS. The network filter fails because it cannot find any hosts configured with the outdated network backing.

Resolution

To resolve this issue, you must update the network configuration in Aria Automation to match the current state of the vSphere environment.

1. Log in to the vSphere Client and identify the correct network backing (e.g., the specific VDS port group) for the network that is causing the failure.

2. Log in to Aria Automation as a Cloud Administrator.

3. Navigate to Infrastructure > Resources > Networks.

4. Locate the network profile and the specific network that is part of the failing deployments.

5. Edit the network configuration to align with the changes identified in Step 1. This may involve updating the network type or re-associating it with the correct backing port group on the VDS.

6. After saving the changes, navigate to Infrastructure > Connections > Cloud Accounts.

7. Run a data collection for the vCenter Server cloud account to ensure Aria Automation synchronizes with the latest infrastructure changes.

8. Retry the machine provisioning.