Why I'm getting duplicated records for the same VDI in the cmdb_ci_vmware_instance table?

Vicente · ‎05-14-2019

Hello, Community.

I'm having an issue and I would like to know why it's happening.
I'm new using the platform and I'm getting familiar with it.

Issue:
Once the schedule job finish its execution, I have duplicated records for the same VDI in the cmdb_ci_vmware_instance table.
Both records have the same object id. (one record is poorly populated and the other one it's completely populated)

I noticed in the Event Logs section, that first is generated the uncompleted record and few seconds later, the fully populated one.

I would like to know the reason why this is happening and how could I prevent this situation.

Your help will be more than welcome.

Thanks.

christianmalone · ‎05-14-2019

It appears one entry is populated by your Mid and the other by System so it seems two different datasources are populating the same table. That should be ok if both are using Identification Reconciliation or coalescing on the same fields. In this case while the object id’s are the CI identification field it’s also a dependent identifier rule - meaning that it needs to find a relationship to the vcenter region/account, computer, and/or virtualization server to correctly identify as unique. My hypothesis is that because Discovery, whether IP schedule, VCenter API call or cloud events, follows these rules and your other datasource is likely NOT correctly building the relationships then Discovery is not seeing them as the same at all. Can you click on the record created by system and confirm what relationships exist? Are they the same as the mid created record? Is it possible another integration such as ForeScout or something is also populating your CMDB?

Vicente · ‎05-15-2019

Hello, Christian.

These are the previews for both records:

This is the one that it's fully populated:

And, yes..there's an integration between SN and a cloud tool for data normalization purpose and for populate info from AWS servers into the CMDB.

Following the event logs preview: