Onboarding VM fails stating 'no placement available to satisfy resource requirement' when the onboarding plan is created using 'Use Placement'

Products

• VMware Aria Suite

Issue/Introduction

This symptoms can occur when a cluster in vCenter is configured with multiple resource pools and at Aria Automation multiple cloud zones are configured pointing towards the resources on the same vSphere cluster
Onboarding tasks validate the placement feasibility for all cloud zones configured in the cluster and not just the cluster to which the VM may confide to
Thus, if either of the cloud zones fail to satisfy the resource requirement for the VM, the onboarding task will fail with message 'no placement available to satisfy resource requirement'

Environment

Aria Automation 8.x

Cause

This is expected behavior, Aria Automation tends to validate the entire cluster and all cloud zones configured on it

Resolution

Below pointers are key when Onboarding a VM when 'Use Placement' is selected

• Ensure enough resources are available on all the cloud zones configured on the shared cluster
• If there are resource pools configured, then if feasible, ensure that the resource pools have the scalable shares options ticked and expandable reservations is ticked to ensure that the resources of the resource pool can scale to the cluster capabilities if required, thus, in case of onboarding, if a certain cloud zone fails to satisfy the requirement, it would look beyond into the cluster capabilities. Here it would provide the resource pool cluster wide capacity not just confide it to its own configured capacities

Additional Information

NOTE: If you don't want to use resource placement in your onboarding plan to enforce resource limits that are defined in the cloud zones or the resource quota policies associated with the project. Then their is no need to select 'Use Placement'. Doing this will violate the resource limits at Cloud zones

• Why scalable shares check box needs to be ticked, can be answered with the doc below:
  https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.resmgmt.doc/GUID-0F6C6709-A5DA-4D38-BE08-6CB1002DD13D.html
  
  When you create a child resource pool, you are prompted for resource pool attribute information. The system uses admission control to make sure you cannot allocate resources that are not available. If you want your shares to scale dynamically when adding or removing VMs, you can select scalable shares.
  as per for the option of expandable reservations, make help the lower limits, as in basic mandate requirements flexible.