VM Storage Policy Displays as ‘None’ for Virtual Machines on vSAN Datastore

Products

• VMware vCenter Server

Issue/Introduction

• The storage policy for virtual machines appears as “None” under VM > Configure > Policies in the vSphere client, even though the VMs reside on a vSAN datastore.

  

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

  

• Attempting to manually reapply the vSAN Default Storage Policy completes successfully, but the changes do not reflect in the UI.

• Navigating to Cluster > Monitor > vSAN > Virtual Objects shows that the correct policy is assigned and all associated objects are in a healthy state.

• This behavior began after updating the FQDN of the ESXi hosts.

• The issue is observed when all hosts in the cluster have their FQDN changed, policy changes stop reflecting in the UI. If at least one host retains the old FQDN, the UI reflects the policy changes as expected.

Environment

VMware vSAN 7.x

VMware vSAN 8.x

VMware vSAN 9.x

Cause

The issue appears to be caused by the FQDN changes made to the vSAN hosts not being fully synchronized with the vCenter Server. While the vSAN cluster continues to function normally and virtual objects remain healthy, the vSphere Client fails to reflect the updated state, resulting in incorrect policy display.

Upon reviewing the Policies and Profiles section, it is observed that the vSAN datastore is reported as non-compliant with any vSAN storage policy. The error message “Container ID is not present” indicates that vCenter Server is unable to correctly identify and associate the vSAN datastore due to the FQDN changes, confirming a sync issue between the updated host identities and vCenter.

Resolution

Reboot the vCenter Server to resynchronize the updated FQDN information of the vSAN hosts. This action allows the vCenter Server to correctly identify the vSAN datastore and reflect the appropriate storage policy assignments in the vSphere Client UI.

Additional Information

If the issue is seen without any host FQDN changes, and rebooting vCenter does not resolve the issue see VM displayed an inconsistent storage policy status.