Need to find the entities causing the precheck failure in Upgrade readiness dashboard.

Available Languages

Updated:October 2, 2026
Document ID:SPLK055231

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk IT Service Intelligence 4.19.1

Description

The Upgrade Readiness Dashboard has an "Open in Search" option, as shown below, which retrieves errors related to precheck failures. This allows us to see the affected objects; however, the error only contains the entity key, which cannot be easily leveraged in entity management.


Error message:

2024-12-30 13:17:10,824+0000 process:3123875 thread:MainThread ERROR [itsi.upgrade_readiness] [itsi_migration_utility_handler:198] [perform_precheck] [transaction_id=d214229aeaef4b31ad55127c7c70192f] [precheck_id=ENT_DSR] [total_count=3] [severity=Major] [category="Entity"] [blocks_upgrade=True] [precheck_failed="Incorrect service linked to entity"]Find out details here[ { "entities_with_dangling_services": ["859bb237-2b35-4e47-adc0-3c0374a80fb9"], "service": "ac6648b1-9a23-450d-a65d-c982b57548b9", "entities_without_right_services": [], "title": "Linux_Prod" }, { "entities_with_dangling_services": [ "762597c8-3f6d-4408-974f-0f5f4c60aca1", "6b6eb258-c456-499d-938b-1924cb5c0bee", "fe0f026f-277d-41b8-885d-2ac730fb85aa" ], "service": "d3a25487-9fa3-4f74-82bf-9c8587fc155d", "entities_without_right_services": [], "title": "Linux" }, { "entities_with_dangling_services": [ "6b6eb258-c456-499d-938b-1924cb5c0bee", "fe0f026f-277d-41b8-885d-2ac730fb85aa", "b0d51420-daea-46ca-91c1-ad7b2ff8820b", "859bb237-2b35-4e47-adc0-3c0374a80fb9", "762597c8-3f6d-4408-974f-0f5f4c60aca1" ], "service": "da-itsi-cp-shared-infra-shared-it-infrastructure", "entities_without_right_services": [], "title": "Shared IT Infrastructure" } ]

Resolution

  1. To find the entities with issues, the following SPL query can be used.
| inputlookup itsi_entities  
| rename _* as *  
| search key IN (  
  "6b6eb258-c456-499d-938b-1924cb5c0bee",  
  "762597c8-3f6d-4408-974f-0f5f4c60aca1",  
  "fe0f026f-277d-41b8-885d-2ac730fb85aa"  
)  
| table title key retired


  1. The key values should be replaced in the above SPL with the entity key values found in the error retrieved from the 'Open in Search' option of the 'Upgrade Readiness' dashboard.
  2. This query helps identify entity titles so they can be located in the "Entity Management page". It also includes the retired field to check whether the entity is in a retired state.
  3. Upon reviewing the results, there are five entities causing the issue were already in a retired state. Since they were retired, they were removed using the Entity Management page >> Retired Entities.
  4. After removing the troublesome entities, the precheck passed as shown below:


 

 


Reference - Upgrade Dashboard

Revision History

Revision Publish Date Comments
1.0
02-Oct-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products