Custom group membership is not honored despite preview shows right members
search cancel

Custom group membership is not honored despite preview shows right members

book

Article ID: 340743

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article provides steps to work around the issue when the created custom group is empty or do not have all members.

Symptoms:

When adding objects to a Custom Group, preview shows right members. But when saving, the created custom group is empty or not having all members.



Environment

VMware vRealize Operations Manager 6.3.x

Cause

Looking at End Point Operations Management adapter instance could observe self-cyclic relationships for the same resource which is discovered by End Point Operations Management adapter instance. <?xml:namespace prefix = "o" />

 

The issue is due to self-cyclic relationships established by some adapters such as End Point Operations Management adapter, OEM Adapter.

 

If the custom groups are not getting updated, check for self-cyclic relationships when the same resource is discovered by multiple adapter instances.

select resource_name,resource_id, internal_id,relationships as text from resource where resource_id='########-####-####-####-########ec0c';

 

22437 | [{"relation":"CHILD","resourceId":{"type":"RESOURCE","uuid":"########-####-####-####-########d717","lduid":"name_of_object-","internalId":22437},"creationTime":1476327081799,"adapterInstan
ceId":7},{"relation":"CHILD","resourceId":{"type":"RESOURCE","uuid":"########-####-####-####-########4277","lduid":" name_of_object - ","internalId":22427},"creationTime":1470541122335,"adapterInstanceId":2
6971},{"relation":"CHILD","resourceId":{"type":"RESOURCE","uuid":"########-####-####-####-########d717","lduid":" name_of_object - ","internalId":22437},"creationTime":1475895088826,"adapterInstanceId":9},{
"relation":"CHILD","resourceId":{"type":"RESOURCE","uuid":"########-####-####-####-########6dc8","lduid":" name_of_object -","internalId":22420},"creationTime":1470541122335,"adapterInstanceId":26971},{"re
lation":"CHILD","resourceId":{"type":"RESOURCE","uuid":"########-####-####-####-########f883","lduid":" name_of_object - ","internalId":22434},"creationTime":1470541122335,"adapterInstanceId":26971},{"relat
ion":"CHILD","resourceId":{"type":"RESOURCE","uuid":"########-####-####-####-########a6a6","lduid":" name_of_object - ","internalId":22352},"creationTime":1470541122335,"adapterInstanceId":26971}]

Note: You can use internal_id or resource_id in where clause and pass the required resource_id.

Resolution

This is a known issue affecting vRealize Operations Manager 6.3. This issue is solved in vRealize Operations Manager 6.4, available at Broadcom Downloads.

To work around this issue, if you do not want to upgrade:

Identify if a resource is discovered by multiple adapter instances. If yes, take note of the internal IDs of both the resources and look for it in Postgres DB for the first level of children.

If there are any self cyclic relationships, i.e., the parent contains itself in the first level children, you should delete the resource which is discovered by second adapter instance until the custom group is updated with the resources you wanted keeping the Keep updated membership option unchecked.