How to create a CI or a Relationship to a CI which have a defined dependency?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2024 12:56 AM
Dear All,
We're struggeling setting up a proper IH-ETL import for CIs which have defined dependencies (e.g. MSFT SQL Instance, Kubernetes Namespace etc.). We are not even able to create a relationship between 2 existing CIs having a dependency. ETL always returns a MISSING_DEPENDENCY error.
Baseline:
All our CIs and relationships are found in non ServiceNow databases. So we have to import them class by class. There is no discovery in place.
Import procedure:
- We start to import the "basic" CIs first, like servers, clusters etc.
- In a second phase, we want to import additional CIs which have dependencies.
- Importing and relate CIs with no dependency works fine
- Class Manager view of a CI with a dependency
How we configured ETL:
- Class Mapping (in this case both CIs are already in the CMDB. We just want to create the relationship)
- Relationship
- Result of the integration run
Partial Load (find the JSON file as attachment)
Warning Log (find the JSON file as attachment)
Does anyone have an idea how to import CIs with dependencies using ETL? Is it even possible to use ETL or do we have to switch to transform maps?
Thanks a lot in advance for your support.
Best Regards
Oliver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2024 01:50 AM
I think you are missing on identification attribute for
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2024 02:03 AM
Hi
Adding the class does not change anything. The MISSING_DEPENDENCY error still pops up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2024 09:56 AM
@OliverTim I have this question too, did you find a solution for the same?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2024 05:38 AM
Hi @Irston Antao
After days of testing we found a solution.
- It is key that the hiearchy of the relationship is according the hierarchy definied in dependent relationships (parent - child). The order in the "classic" relationship definition may be different. The dependent relationship is the "master".
- The Kubernetes Namespace class is shipped with an error. The dependent relationship is the wrong way. Instead von Cluster (Parent) and Namespace (Child) it is the other way.
Now it works fine.
Kind Regards
Oliver