Notifications

8 views

Description

After IP discovery on the Server running on AWS created a new relationship with an incorrect duplicated VM instance.  The discovery created duplicated VM instances due to the issue in PRB1385597.

Relationship creation logic didn't account for the duplicated record and just picked up a random VM with matching "object_id" and happened to pick the duplicated record. 

Resolution

Relationship creation logic didn't account for the duplicated record and just pick up a random VM with matching "object_id" and happened to pick the duplicated record. ( Issue is related to PRB1406405 )

Workaround,
Modify the "DiscoveryAWSRelationshipSensor" script includes with the following change to have it pick up the right VM,


Changed line 63,

FROM:

if(relationsGlideRecord.parent.object_id.indexOf(valueToSearch) != -1){



TO:


if(relationsGlideRecord.parent.object_id.indexOf(valueToSearch) != -1 && JSUtil.nil(relationsGlideRecord.parent.duplicate_of)){




Article Information

Last Updated:2020-06-22 01:15:27
Published:2020-06-19