logo

NJP

The "discovery_source" for OS Package CI is set to "empty" by Discovery due to which CMDB Health job marks the CI that has same OS package name as "Duplicate"

Import · Oct 14, 2020 · article

Issue: The "discovery_source" for OS Package CI is set to "empty" by Discovery due to which CMDB Health job marks the CI that has same OS package name as "Duplicate"

Steps to reproduce:

1. Trigger a Solaris CI discovery.

2. Navigate to cmdb_ci_os_packages_list.do and filter for the CI for which discovery was executed.

- "Discovery Source" field for the CI's populated will be "empty".

3. The OS package name on one Solaris CI can be same as the one on another Solaris CI.

4. The CMDB Health job ignores the records that have discovery_source. Due to "discovery_source" being "empty" when CMDB Health job runs it captures them as duplicates. (which in turn is not a duplicate)

Resolution:

Navigate to Sensors >> Solaris - OS Packages

Replace the processJSON function with the below script,

processJSON: function() { if (JSUtil.nil(related_data.packages)) return; var sourceName = gs.getProperty('glide.discovery.source_name', "ServiceNow"); related_data.packages.forEach(function(obj) { obj.discovery_source = sourceName;

});

View original source

https://www.servicenow.com/community/itom-articles/the-quot-discovery-source-quot-for-os-package-ci-is-set-to-quot/ta-p/2324188