Error "Underlying system error: com.vmware.vim.binding.vim.fault.DatacenterMismatch" When Creating or Importing VMs in Organization VDC linked to Provider VDC with Resource Pools from multiple Datacenters
search cancel

Error "Underlying system error: com.vmware.vim.binding.vim.fault.DatacenterMismatch" When Creating or Importing VMs in Organization VDC linked to Provider VDC with Resource Pools from multiple Datacenters

book

Article ID: 385275

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • The creation or import of a VM in an Organization VDC linked to a Provider VDC that has resource pools from multiple datacenters fails with the Error: "Underlying system error: com.vmware.vim.binding.vim.fault.DatacenterMismatch".
  • Under /opt/vmware/vcloud-director/logs/vcloud-container-debug.log, you see messages similar to:

    (com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:XXXXX-XXXXX-XXXXX-XXXXX)
    com.vmware.ssdc.library.exceptions.GenericVimFaultException: Underlying system error: com.vmware.vim.binding.vim.fault.DatacenterMismatch
    vCenter Server task (moref: task-XXXX) failed in vCenter Server '<vCenterFQDN>' (XXXXX-XXXXX-XXXXX-XXXXX).
    at com.vmware.ssdc.library.vim.LmVim.createGenericVimFaultException(LmVim.java:330)
    Caused by: (vim.fault.DatacenterMismatch) {faultCause = null,faultMessage = null,invalidArgument = (vim.fault.Argument) [(vim.fault.Argument) {dynamicType = null,dynamicProperty = null,entity = ManagedObjectReference: type = Folder, value = group-XXXX, serverGuid = null,inputDatacenter = ManagedObjectReference: type = Datacenter, value = <Name of datacenter-X>, serverGuid = null}],expectedDatacenter = ManagedObjectReference: type = Datacenter, value = <Name of datacenter-Y>, serverGuid = null}

Environment

VMware Cloud Director 10.X

Cause

  • Currently, it is not supported to use resource pools from multiple datacenters when creating or importing VMs. Although it’s possible to add resource pools from different datacenters to the Provider VDC, and even enable the "Elasticity" allocation model, the functionality for cross-datacenter usage is not supported.

Resolution

  • While resource pools from multiple vCenter datacenters can be added to a Provider VDC, the associated Organization VDC must use resource pools from a single datacenter only. 
  • Elastic VDC creation is not supported across multiple vCenter datacenters. 
  • Therefore, ensure that only resource pools from a single datacenter are added to the Provider VDC to allow the Organization VDC to function correctly.
  • For more information refer: Create an Organization Virtual Data Center in VMware Cloud Director