Notifications

97 views

Description

There are CMDB Relationship Type records included out-of-the-box that are dependencies of Discovery and Service Mapping Patterns

Relation types that are dependencies of Discovery and Service Mapping Patterns can be renamed or removed from cmdb_rel_type table. Code that has the relationship type sys_id or Name hard-coded will either break, or insert invalid relationship records.

At least the following records need to be protected:

Applicative Flow To::Applicative Flow From - 85d98503ff100200d699ffffffffff8c
Cluster of::Cluster - a99d39118f10310091769012cbbe4429
Contains::Contained by - 55c95bf6c0a8010e0118ec7056ebc54d
Depends on::Used by - 1a9cb166f1571100a92eb60da2bce5c5
Hosted on::Hosts - 5f985e0ec0a8010e00a9714f2a172815
Impacts::Impacted By - 11ee47317f723100ed1c3b19befa91f9
Implement End Point To::Implement End Point From - 45e94a74532221007c949096a11c0861
Runs on::Runs - 60bc4e22c0a8010e01f074cbe6bd73c3
Use End Point To::Use End Point From - e7490a74532221007c949096a11c08b2
Connects to::Connected by - 5599a965c0a8010e00da3b58b113d70e ???
Virtualized by::Virtualizes - d93304fb0a0a0b78006081a72ef08444
Instantiates::Instantiated by - 1bb40e370a0a0b323d85a1ce84f8feae
...and there are more.

Once the OOTB records are deleted, it is possible that new records of the same name are created with different sys_ids, which also breaks any code with hard-coded sys_ids.

This also breaks other OOTB records in other tables that reference relationship type using the original sys_ids, including:
cmdb_metadata_containment
cmdb_metadata_hosting
cmdb_rel_filter
cmdb_rel_type_suggest
and others...

Steps to Reproduce

  1. Open Configuration - Relationships - CI Relation Types /cmdb_rel_type_list.do
  2. Delete entries, such as "Instantiates::Instantiated by" which is used by the "Windows OS - Post Sensor" post pattern script
  3. Alternatively, rename the parent and/or child descriptor of one, such as "Virtualized by::Virtualizes" to "Virtualised by::Virtualises", which a UK company may chose to do. 

In this example, a discovery of a virtual Windows Server discover will cause cmdb_rel_ci records to be inserted with broken relationship type references, and those broken relations will go on to cause problems for the Identification Engine and CMDB health.

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.


Related Problem: PRB1386982

Seen In

SR - IntegrationHub - Jenkins Integration r1 - v1.2.0
SR - IntegrationHub - JIRA Service Desk Integration r2 - v2.0.7
SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Check Point Integration - New York 2019 Q3
SR - SIR - ElasticSearch Integration - Madrid 2019 Q1
SR - SIR - Exchange Online Integration - New York 2019 Q3 2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response Flow Designer Content - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Splunk Sighting Search Integration - Madrid 2019 Q1
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - SIR - VirusTotal Integration - New York 2019 Q3
SR - SIR - WHOIS Integration - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Intended Fix Version

Quebec

Fixed In

New York Patch 11
Orlando Patch 8
Paris Patch 1

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-07-31 07:42:35
Published:2020-07-31