The day2 policy doesn't apply to VMs whose hasSnapshot property not available.

Products

• VMware Aria Suite

Issue/Introduction

When provisioning a new virtual machine (VM) with Aria Automation, a 'hasSnapshot' property is included as part of the VM's configuration. This property is used by a day-2 policy to determine specific actions for the VM. The day-2 policy performs a one-time check after the VM is created. However, since the 'hasSnapshot' property is only updated during the daily data collection process (and not at the time of provisioning), the day-2 policy cannot apply until this property is available.

Environment

VMware Aria Automation8.16.x

Cause

Each VM has a Custom Property section, user can look up hasSnapshot there, if this property doesn't exist, day2 policy doesn't apply.

Resolution

Workaround 

 Adding "Or name not equal to dummy123" to the existing criterion. It proved to work by customer during the meeting.
Note: dummy123 is any string that deployments wont be named

 

 

This policy won't be kicked out automatically when resources stored in catalog-db received hasSnapshot property, but clicking a deployment on UI will trigger the policy running and update day2 actions for this deployment's resources