Dependent Ci management is not working

Deepak61
Tera Contributor

I'm having trouble understanding and getting to make the Dependency CI management work. I've enabled the property  "cmdb.dependent.ci.cascade.op.enabled" mentioned in the documentation https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...
and also I have enabled the  life-cycle rules . Still, whenever I retire a Linux CI using the cmdb data manager policy to retire.  it is hosting a apache web server, but the web server is not getting retired, nor can I see the web server in the ledger cmdb_dependent_ci_ledger as mentioned in the documentation.
I have also ran the following scheduled jobs after retiring the Linux.

1. CMDB DependentCI Policy Processor
2. CMDB Cascade Retire Dependent CIs

There still no records in the cmdb_dependent_ci_ledger table even after the linux server is retired. 
Can someone help me with this? 

25 REPLIES 25

Kieran Anson
Kilo Patron

It's not mentioned in that document, assumingly because the default is "true", but check you don't have a system property of 'cmdb.dependent.ci.cascade.retire.enabled' set to false. If you don't find a system property with that name, then you should be ok.

 

It's not very clear, but 'dependent' relationships need to be defined in CI Class Manager, using the example of Web Server you can see the dependencies below. You need to create a dependency between Linux and Web Servers. CMDB dependent relationship rules (servicenow.com)

 

KieranAnson_0-1714388254541.png

 

Hello Kieran,

There isn't any property named like that set to 'false'. The relationship already exists out-of-the-box (OOB), as shown in the provided screenshot example. It's a 'runs on:: runs' relationship.

Screenshot 2024-04-29 163631.png

However, when the Linux device is retired, the web server isn't being retired as expected. This behavior goes against what's explained in the documentation at
https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag....

"This behavior goes against what's explained in the documentation " - In the documentation, which bit in particular is contradicting?

The Cascade-retire dependent CIs section. 

Deepak61_0-1714390600656.png

If I understand correctly, when the Linux CI is retired, the retirement should cascade to all the dependent CIs under the Linux server.