Does Discovery change the status of a CI to only installed or retired on updates?

sanjeev20 · ‎05-20-2022

Hi All,

I have a question. When discovery discovers any server CI , it creates a new CI record in the server class and the Status field of this CI is set to "Pending install" as this was default value set for this field.

However when the discovery runs again for the same device , it is changing the Status of this CI between Installed and Retired in multiple runs.

I just want to understand that does discovery change the status of a CI only to Installed or Retired. Also we have many more statuses available in the system like Absent, In Maintenance, on order, Pending repair etc.. How does these values are selected for any CI. Is it not via discovery and through some other process automation? And if it is happening via process automation , how do we ensure that discovery status update should be aligned with it.

Please note we have included Status attribute in the reconciliation rule of the Server class.

Regards,

Sanjeev Kumar

Rahul Priyadars · ‎05-22-2022

It seems that some known behavior ..

May be these KB can help you.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0951844

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0998780

Steps to Reproduce

Run Discovery Schedule for Cloud Resources (Vcenter)
For ESX Servers the status is flip flopping between retired and installed.

Regards

RP

View solution in original post

emir · ‎05-20-2022

Discovery should set it to 1, which is Installed. Can you check that CI and see what the actual numerical value of the status is? Did someone change those?

sanjeev20 · ‎05-22-2022

I have check and can confirm we are using OOB status choices.

Rahul Priyadars · ‎05-22-2022

OOTb discovery sets to install. It never flips the status to retired ootb. Check ur audit log how it's flipping . Regards RP

sanjeev20 · ‎05-22-2022

Hi Rahul,

Its a ESX server for which the state is flipping between Installed and retired. We have one service account mid_discovery which is used for discovery and the logs shows that this account is updating it multiple times.