"Non-elastic VDC "XXXX" does not support migrating VMs to a non-default resource pool. "moref://XXXX/ResourcePool#resgroup-XXXX". Please use the default resource pool "moref://XXXXX/ResourcePool#resgroup-XX" error when migrating VMs in Cloud Director.
search cancel

"Non-elastic VDC "XXXX" does not support migrating VMs to a non-default resource pool. "moref://XXXX/ResourcePool#resgroup-XXXX". Please use the default resource pool "moref://XXXXX/ResourcePool#resgroup-XX" error when migrating VMs in Cloud Director.

book

Article ID: 325660

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
  • When migrating VMs in VMware Cloud Director, the below error is seen:
"Non-elastic VDC "XXXX" does not support migrating VMs to a non-default resource pool. "moref://XXXX/ResourcePool#resgroup-XXXX". Please use the default resource pool "moref://XXXXX/ResourcePool#resgroup-XX"
  • Organizations are using an Allocation Pool model.
  • In /opt/vmware/vcloud-director/logs/vcloud-container-debug.log, the following errors are logged: 
    • Error: Please use the default resource pool "moref://XXXX/ResourcePool#resgroup-XX".
              at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeImpl.init(PlacementServiceFacadeImpl.java:480)
              at com.vmware.vcloud.placementfacade.impl.PlacementServiceFacadeFactoryImpl.createPlacementServiceFacade(PlacementServiceFacadeFactoryImpl.java:122)
    • Error: Please use the default resource pool "moref://XXXX/ResourcePool#resgroup-XX".
              at com.vmware.ssdc.util.LMException.wrap(LMException.java:128)
              at com.vmware.ssdc.library.ExceptionFactory.createFromMultiple(ExceptionFactory.java:32)
              at com.vmware.vcloud.common.future.FutureUtil.waitForFutures(FutureUtil.java:87)
              at com.vmware.vcloud.common.future.FutureUtil.waitForFutures(FutureUtil.java:96)
              at com.vmware.vcloud.vapp.impl.VAppServiceImpl.migrateVmsTask(VAppServiceImpl.java:3787)
              at com.vmware.vcloud.vapp.impl.VAppServiceImpl.executeTask(VAppServiceImpl.java:777)
              at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase


Environment

VMware Cloud Director 10.x

Cause

This is expected behaviour as the two resource Pools that are being used are not elastic.

An Organization VDC cannot use the resources in both/multiple clusters when the elastic setting is disabled.


Resolution

To resolve the issue, enable the elastic option so that the Organization VDCs can use resources from multiple clusters:
  1. On the Provider Portal, click on the Administration Tab.
  2. Under the Settings tab, click General.
  3. On the section for Other click the Edit button.
  4. Enable the toggle for Make Allocation Pool Organization VDC's elastic.
  5. Click Save.
  6. Wait for a few minutes for the new change to be applied.
  7. Migrate the VMs.


Additional Information

The following documentation explains more about the elasticity setting in Cloud Director:

https://docs.vmware.com/en/VMware-Cloud-Director/10.3/VMware-Cloud-Director-Service-Provider-Admin-Portal-Guide/GUID-2CE6C061-97FD-4963-A5D9-98109D45D6C3.html