Dependent Ci management is not working

[Deepak61]

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? 

[Eric148]

Hello, thank you for the reply, but my issue is after running CMDB Data Manager Retire Policy Processor and the task is created, approving the task does not retire the dependent CIs (no change to Life Cycle Stage or Life Cycle Stage Status).  The dependent CIs show no change at all (including Updated date/time).

[bkprasanna]

Hi Eric,

This entire process has 2 stages

1st stage : After running CMDB Data Manager Retire Policy Processor a task will get generated When you approve the task ( which is for parent CIs) who's life cycle stage and life cycle stage status will  be set to "End of life" and "Retired" respectively.

2nd satge : Scheduled jobs "CMDB DependentCI Policy Processor" and "CMDB Cascade Retire Dependent CIs" will trigger the second task as per the schedule.or even if you try to execute -on demand..this task generation will take some time to add all the dependent CIs to ledger table and then it processes and create the task.

Also make sure you have created the below system properties to true for the respective scheduled jobs

cmdb.dependent.ci.cascade.retire.enabled

cmdb.dependent.ci.cascade.op.enabled'

[Eric148]

Thanks, I have setup both of those sys properties already.  

sys_properties.list:
cmdb.dependent.ci.cascade.op.enabled = true
cmdb.dependent.ci.cascade.retire.enabled = true

Using computer CI,
I set the Life Cycle Stage = End of Life and Life Cycle Stage Status = Retired.
I run Scheduled Job: CMDB Cascade Retire Dependent CIs.
This populates cmdb_dependent_ci_ledger with the dependent CIs to be retired as expected.
I run Scheduled Job: CMDB DependentCI Policy Processor (this creates CMDBTASK0001007 with dependent CIs to be retired as expected)
I approve the task and the dependent CIs are cleared from the list. The task shows successful but the dependent CIs do not retire.

[bkprasanna]

Hi Eric,

Check the status of  the dependent CI's (on;y which got added in the dependent CI task) after approval the life cycle stage and life cycle stage status of the dependent CI will  be set to "End of life" and "Retired" respectively.

[Eric148]

Hey, that is the part that is not updating after the task is completed.  The Life Cycle Stage and Life Cycle Stage Status of all of the dependent CIs that showed in the task are blank still and the Updated field still shows a date from earlier this year like before as well.