Discovery Log Warning - Cannot find CI: ###### in CMDB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2022 07:02 AM
Currently, I am working to set up Discovery for my organizations infrastructure, and we came across a fairly unique situation where each of the Hyper-V servers are created from the same image, and set up in a way that they have the same Serial Numbers. I've had similar issues before, so to resolve this I created a Hybrid Identification rule to replace the Serial Number/Serial Number type Identifier with a mix of Serial Number/Type and Server name.
This is working as far as discovering the CI's and creating them correctly, but I am receiving the following warning message close to once per server in the Discovery Logs: "Cannot find CI: 31fe07421b6ff4149e9ecbb8624bcb33 in CMDB".
It is the same sys_id in each of the warning logs. I have searched for the sys_id in the CMDB, in both our productions and non-prod instances, and cannot find it anywhere. I have looked through the community but haven't found much information outlining this Warning message. Does anyone know what this is and how to resolve it?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2022 10:54 AM
Was the root cause of this ever found? Seeing the same issue and was hoping that the root cause was identified and could be shared.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2022 12:50 PM
Ended up figuring it out. This was caused by a relationship still in the cmdb_rel_ci table for the related hardware record of a vCenter CI that was being discovered. When running discovery on the IP the vCenter CI was discovered but not the associated hardware CI. The hardware record was actually archived under ar_cmdb_ci_win_server so did still exist just not under a cmdb_ci extended table.
