Dependent Ci management is not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2024 03:43 AM - edited 04-29-2024 03:52 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2024 05:13 AM
What helps us was to set the runtime configuration for OOTB cascade retirement policy to published, and runs as
table
cmdb_data_management_policy_runtime_attributes
policy: Dependent CI - Retire
Fill "runs as" and set the status to Published (via servicenow Utils😋)
dont forget to enable retirement definitions
cmdb_retirement_custom_definitions
otherwise CI will not be enabled
😉