Storage policy fails deletion after associated objects are removed in vCenter Server.

Products

• VMware vCenter Server 6.0
• VMware vCenter Server 7.0
• VMware vCenter Server 8.0
• Tanzu Kubernetes Runtime

Issue/Introduction

• Deleting a VM Storage Policy errors with "Delete VM Storage Policy Failed: The resource '####-####-####-####-############' is in use'"
• Error: 'Delete VM storage policy Failed,The resource is in use', when deleting policies previously used by OpenShift, VKS, or other CSI-based Kubernetes distributions.

1. 1. No VMs are associated to the storage policy
   2. No PVCs are associated to the storage policy
   3. No WCP supervisors or namespaces are associated to the storage policy.

• /var/log/vmware/vmware-sps/sps.log contains the following log entries:
  
  ERROR opId=########-#######-####-#####-##:######## com.vmware.pbm.profile.impl.ProfileManagerImpl - Profile ####-####-####-####-############ is still associated with # entities.
ERROR opId=########-#######-####-#####-##:######## com.vmware.pbm.profile.impl.ProfileManagerImpl - Profile ####-####-####-####-############ is still associated with entity ####-####-####-####-############

Environment

VMware vCenter 6.x
VMware vCenter 7.x
VMware vCenter 8.x
VMware Cloud Native Storage (CNS)

Cause

There is likely a stale FCD association(s) with the VM Storage Policy. One cause of stale FCD associations could be from following Migrating VMs/Volumes across Datastores in vSphere with Tanzu / vSphere Kubernetes Supervisor

Resolution

Please contact a Broadcom support for assistance with this issue.