Custom Group Displays Incorrect Custom Properties on VMs in Aria Operations
Article ID: 430095
Updated On:
Products
Issue/Introduction
In VMware Aria Operations, when a Custom Group is configured to assign a Custom Property, virtual machines (VMs) may be forced out of the custom group, resulting in the wrong or missing custom property being displayed.
This issue occurs when the Custom Group has the following configuration:
Group Type: Environment
Define Membership Criteria: Select the Object Type that matches all of the following criteria: Virtual Machine
Relationship > Descendant of > is [Value]
Objects to always include/exclude: Includes a list of specific objects to exclude.
Assign Custom Properties:
Property name: [Value] > Type: String
Value: [Value] * Reset value: None
Environment
VMware Aria Operations 8.18.x
Cause
In VMware Aria Operations, Manual Exclusions take strict precedence over dynamic membership criteria.
If an object is explicitly listed in the "Objects to always exclude" section of a Custom Group definition, the group’s associated policies and property assignments will not be applied to that object, regardless of whether the object matches the dynamic tagging or naming rules. In this scenario, the VMs remained stuck with a stale site value because the group was barred from claiming them.
Resolution
To resolve this issue, you must remove the affected VMs from the Custom Group settings (step 3) Objects to include/exclude list.
-
Log in to the VMware Aria Operations UI.
-
Navigate to Environment > Custom Groups.
-
Select and edit the affected Custom Group.
-
In the group configuration wizard, navigate to the "Objects to always exclude" section.
-
Identify the affected VMs in the list. Click the X (Remove) button next to these entities to remove them from the exclusion list..
-
Save your changes.
Note: The system will typically update the properties during the next standard collection cycle (default is 5 minutes).
Additional Information
KB articles for reference:
Feedback
