VM relocated between resource pools in VCD appears in vCenter > Datacenter > root directory in the VM and template view
Article ID: 416781
Updated On:
Products
Issue/Introduction
When a Service Provider administrator migrates a Virtual Machine (VM) between two different Resource Pools using the VMware Cloud Director (VCD) Provider UI, the VM's placement in the vCenter Server "VMs and Templates" inventory view is incorrect.
Instead of appearing under the correct destination Resource Pool, the relocated VM object is placed at the root level of the vCenter Datacenter object.
This behavior is observed in environments where an Elastic Provider VDC (PVDC) is configured to span resources from multiple vCenter Datacenter objects.
Environment
-
VMware Cloud Director 10.x
-
VMware vCenter Server 8.x
Cause
This issue is caused by an unsupported Provider VDC (PVDC) configuration.
The core problem is that the Elastic PVDC is configured to consume resources (Clusters and their child Resource Pools) from two or more different vCenter Datacenter objects within a single or multiple vCenter Server instances.
VMware Cloud Director's Elastic PVDC feature is designed to span multiple clusters within a single vCenter Datacenter object. When a VM is migrated between resource pools that belong to different vCenter Datacenters, VCD cannot correctly reconcile the VM's inventory placement, as this action crosses a fundamental vCenter inventory boundary.
This architectural conflict results in vCenter Server placing the VM object at the root of the Datacenter inventory tree it was moved to.
Resolution
This configuration is not supported by VMware Cloud Director.
To permanently resolve this issue and ensure correct VM inventory placement during migrations, the Provider VDC (PVDC) must be re-designed. The PVDC must be configured to only include clusters and resource pools that belong to a single vCenter Datacenter object.
The officially supported configuration for an Elastic PVDC is to span multiple clusters and resource pools, provided they all reside within the same vCenter Datacenter.
Additional Information
Feedback
