Aria Operations Custom Groups display inconsistent policy information between List and Summary views

Products

• VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

In VMware Aria Operations (formerly vRealize Operations), users may observe a discrepancy in the assigned policy for Custom Groups.

Symptoms:

• In the Custom Groups list view, the "Policy" column shows an unexpected policy (e.g., a parent group's policy) being applied.

• Specific alerts from the original policy fail to trigger because the inherited policy takes precedence.

• When opening the Summary or Edit window for the same Custom Group, the UI incorrectly displays the original, locally assigned policy.

• The backend (PostgreSQL/Database) correctly reflects the intended policy hierarchy and priority, confirming the issue is isolated to the User Interface.

Environment

VMware Aria Operations 8.18.X

Cause

This is a UI display inconsistency where the List view reflects the actual active policy (based on inheritance and priority), while the Edit/Summary views only show the locally assigned policy without accounting for parent-level overrides.

Resolution

This issue is identified as a UI bug and is tentatively planned to be addressed in a future release.

Workaround/Verification Steps:

1. Check Policy Priority: Navigate to Configure > Policies > Policy Definitions and click Reorder Policies. Ensure that parent group policies do not have a higher priority than child group policies if you wish to avoid inheritance overrides.

2. Verify Membership Criteria: Ensure that "Define Membership Criteria" filters do not include obsolete object types (e.g., from old Management Packs). If a filter defaults to "All" due to missing object types, it may inadvertently include other groups as children, triggering inheritance.

3. Database Validation: To confirm the actual assigned policy in the backend, a technical support engineer can run a SQL query against the kv_policy and resource tables in the Postgres database.