VM displayed an inconsistent storage policy status

Products

• VMware vCenter Server

Issue/Introduction

• The VM Storage Policies interface does not show the VM being assigned to the Default vSAN Storage Policy and instead shows "None".

  

• Reviewing the VM configuration shows the policy applied as “Datastore Default” for VMs on vsanDatastore

  

• sps.log on vCenter will contain entries similar to the following:

2025-10-09T20:10:03.116Z [pool-7-thread-2] ERROR opId=q-####:VmProfileAssignmentPropertyProviderAdapter:14941-###-h5:70001970 com.vmware.spbm.domain.util.EntitySubjectBuilder - Invalid entity subject: EntitySubject{entity = (pbm.ServerObjectRef) {
   dynamicType = null,
   dynamicProperty = null,
   objectType = virtualDiskId,
   key = vm-#####:2019,
   serverUuid = null
}, profile = null, errorCause = com.vmware.pbm.exception.NoAssociatedProfileException: profileID is null for entity vm-#####:2019, storageId = null, vmObject = null, vmInstanceUuid = null, isOnObjectBasedStorage = false, schemaNamespace = null, tagInfo = null, datastoreType = null}
com.vmware.pbm.exception.NoAssociatedProfileException: profileID is null for entity vm-#####:2019

Environment

vSAN (All versions)

Cause

When the VM was being created, or a policy reconfigure task was performed, the sps service was not running or was in an error state on vCenter. 

If SPS is down or in an error state at the time the VM is created or policy change performed the policy association will not be updated, but will not result in any failure for the VM creation operation. The indication will be seen as no policy being associated with the VM.

Resolution

• Edit the VM Storage Policies by right clicking on the VM and selecting "Edit VM Storage Policies..."
  
• Select the vSAN Default Storage Policy
  
• Click OK
• Verify the policy is displayed correctly

Additional Information

If the issue has presented after changing the FQDN of vSAN hosts, please see VM Storage Policy Displays as ‘None’ for Virtual Machines on vSAN Datastore.