VM's show "No policy assigned" and a red compliance warning after Cross vCenter vMotion to vCenter 8.x

Products

• VMware vCenter Server

Issue/Introduction

environment, virtual machines (VMs) display a red compliance warning in the vSphere client. The "VM Storage Policy Compliance" column for these VMs incorrectly shows a status of "NONE" instead of the expected "Datastore Default" policy

 

Environment

 

• vCenter Server 7.x

• vCenter Server 8.x

 

Cause

This is a known cosmetic UI issue. When a VM is migrated using Cross vCenter vMotion, the vSAN datastore correctly applies the "Datastore Default" policy. However, the Storage Policy-Based Management (SPBM) service fails to properly record this policy association in its database. This discrepancy leads to the vSphere client displaying the misleading "NONE" status and a red compliance warning, even though the VM's storage policy is correctly applied and the VM is fully compliant.

Resolution

This is a cosmetic issue and does not impact the functionality, performance, or data integrity of the virtual machines. The VMs are correctly protected by the default vSAN datastore policy. You can safely ignore the red compliance warning.

A permanent fix for this behavior has been submitted to engineering and is expected to be included in the VCF 9.1 release.

Additional Information

 

• This issue is specific to the vSphere client's display. The underlying VM and its storage are correctly configured and in a healthy state.

• No action is required from the user, as the fix will be provided in a future product update.