Error: "The object 'vim.ResourcePool' has already been deleted" during VM deployment | vCenter Server

Products

• VMware vCenter Server
• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Virtual machine deployments initiated through third-party applications (such as Parallels RAS) or automated workflows fail with cloning errors. This typically occurs after configuration changes to the cluster's Distributed Resource Scheduler (DRS) settings.

• Deployment tasks fail with the following error:

  • The object 'vim.ResourcePool:resgroup-####' has already been deleted or has not been completely created.

• The vCenter Server vpxd.log contains entries similar to:

  • var/log/vmware/vpxd/vpxd.log
info vpxd[####] [Originator@6876 sub=vpxLro] [VpxLRO] -- BEGIN lro-#### -- vim.ResourcePool.createVm 
info vpxd[####] [Originator@6876 sub=vpxLro] [VpxLRO] -- FINISH lro-#### -- error: vim.fault.ManagedObjectNotFound

• Third-party applications (e.g., Parallels RAS) report invalid or stale Managed Object References (MoRef) during cloning.

Environment

VCF Automation

VMware vSphere ESXi 7.x, 8.x

VMware Cloud Foundation 5.x

Cause

Disabling vSphere Distributed Resource Scheduler (DRS) on a cluster automatically deletes the resource pool hierarchy. This action purges the existing Managed Object References (MoRefs) for those pools. External applications that cache these MoRefs will attempt to target a deleted object, resulting in the ManagedObjectNotFound error. Disabling VMware Distributed Resource Scheduler for a Cluster

Resolution

To resolve this issue, the resource pool hierarchy must be restored or recreated and the third-party application inventory must be updated:

1. Enable vSphere DRS on the affected cluster.
2. Recreate the previously deleted Resource Pools on the cluster.
3. Refresh the third-party application's configuration or inventory cache to ensure it selects the MoRef of the newly created Resource Pool.
4. To prevent future hierarchy loss, set DRS to Manual instead of Disabled.

Additional Information

• For instructions on preserving resource pools, see the official VMware documentation regarding Retaining resource pools when disabling VMware DRS clusters.
• Review Contact Broadcom Support if the issue persists after refreshing the application cache.