Unable to disable workload management after disabling DRS on the cluster in vSphere with Tanzu.

Products

• VMware vSphere with Tanzu

Issue/Introduction

• Disabling a WCP cluster after DRS has been disabled results in failure. 
• Users will see errors as follows in the /var/log/vmware/wcp/wcpsvc.log

2022-10-10T13:26.586Z error wcp [workload/vcinvnt.go:151] [opID=CLUSTER_NAME] Failed to find resource pool for workload ServerFaultCode: The object 'vim.ResourcePool:resgroup-1234' has already been deleted or has not been completely created. Err %!v(MISSING)
2022-10-10T13:38:31.581Z error wcp [workload/workload_impl.go:1498] Workload CLUSTER_NAME is already being removed

 

• Users will see the following, or similar, logging in the /var/log/vmware/vpxd/vpxd.log
  

2022-10-10T13:26.586Z info vpxd[06272] [Originator@6876 sub=Default opID=wcp-6245a1a1-68] [VpxLRO] -- ERROR lro-577005 -- AuthorizationManager -- vim.AuthorizationManager.setEntityPermissions: vmodl.fault.ManagedObjectNotFound:
--> Result:
--> (vmodl.fault.ManagedObjectNotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> obj = 'vim.ResourcePool:resgroup-1234'
--> msg = ""
--> }
--> Args:
-->
--> Arg entity:
--> 'vim.ResourcePool:resgroup-1234'
 

• NOTE: This error may be encountered if other vSphere objects cannot be found due to incorrect order of deletion. It is important to check the /var/log/vmware/wcp/wcpsvc.log to identify where the failure is occurring prior to running the workaround noted in this KB.

Environment

1. vCenter Server
   VMware vSphere 7.0 with Tanzu

Cause

This failure occurs because the resource pools backing the Namespace objects in vSphere inventory are provided by DRS. When DRS is disabled, the association to the resource pool can not longer be found, leading to a failure to remove the Namespace object.

Resolution

Contact Broadcom Support to work with them to resolve the issue.