Unable to import VM from vCenter in vCD, getting error: NO_FEASIBLE_PLACEMENT_SOLUTION

Products

• VMware Cloud Director

Issue/Introduction

While importing VM from vCenter, the task is failing with below error in vcloud-container-debug.log file:

com.vmware.vcloud.api.presentation.service.InternalServerErrorException: The operation failed because no suitable resource was found. Out of 10 candidate hubs:
1 hubs eliminated because: No valid storage containers found for VirtualMachine "VM_UUID". All 74 available storage containers were filtered out as being invalid.
9 hubs eliminated because: Only contains rejected VM Groups (s) : [[###########] ] Rejected hubs: resgroup-######, resgroup-######, resgroup-#####, resgroup-#####, resgroup-######, resgroup-######, resgroup-#####,resgroup-#####, resgroup-####
Storage containers were rejected for the following reasons: 
73 storage containers rejected because: They do not support the required storage policy: <Storage_Policy>. Rejected storage containers: <Storage Container Names>
at com.vmware.vcloud.placement.PlacementExceptionHandler.convertPlacementException (PlacementExceptionHandler.java: 78)
at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeImpl.computePlacementSolution (PlacementServiceFacadeImpl.java: 1057)
at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeImpl.computePlacementSolution (PlacementServiceFacadeImpl.java: 1040)
at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeImpl.getPlacementState (PlacementServiceFacadeImpl.java: 929)
at com.vmware.vcloud.vdc.impl.CopyContentsActivity$CopyContentsPhase.copyVAppContents (CopyContentsActivity.java: 911)
at com.vmware.vcloud.vdc.impl.CopyContentsActivity$CopyContentsPhase.invoke (CopyContentsActivity.java: 399)
at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase (ActivityRunner.java: 175)
at com.vmware.vcloud.activity.executors.ActivityRunner.run (ActivityRunner.java: 112)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call (Executors.java: 515)
at java.base/java.util.concurrent.FutureTask.run (FutureTask.java: 264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java: 1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java: 628)
at java.base/java.lang.Thread.run (Thread.java: 829)
Caused by: com.vmware.pbm.placement.PlacementException: PlacementException NO_FEASIBLE_PLACEMENT_SOLUTION
at com.vmware.vcloud.placement.engine.impl.PlacementSolverImpl.constructPlacementException (PlacementSolverImpl.java: 138)
at com.vmware.vcloud.placement.engine.impl.PlacementSolver Impl.ensureHubAvailability (PlacementSolverImpl.java: 750)
at com.vmware.vcloud.placement.engine.impl.PlacementSolverImpl.solve (PlacementSolverImpl.java: 182)
at jdk.internal.reflect.GeneratedMethodAccessor8868.invoke (Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java: 43)
at java.base/java.lang.reflect.Method.invoke (Method.java: 566)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection (AopUtils.java: 344)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint (ReflectiveMethodInvocation.java: 198)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed (ReflectiveMethodInvocation.java: 163)
at com.vmware.vcloud.common.diagnostics.GenericMethodDiagnosticsInterceptor.invoke (GenericMethodDiagnosticsInterceptor.java: 37)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed (ReflectiveMethodInvocation.java: 186)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke (JdkDynamicAopProxy.java:241)
at com.sun.proxy.$Proxy1075.solve (Unknown Source)
at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeImpl.computePlacementSolution (PlacementServiceFacadeImpl.java: 1055)

Environment

VMware Cloud Director 10.6.x

Cause

The default VM Placement policy of the OvDC is not supporting the storage policy.

Resolution

Change the OvDC VM Placement policy to the one which supports the required storage policy.

• Login to vCD Provider Portal.
• All Organization VDCs > search and open the concerned OvDC.
• Update the VM Placement policy which supports storage policy that is needed to be used for the VM.