Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Server operational status changing from Retired to Non-Operational

aislingo
Tera Contributor

‎12-19-2022 04:19 AM

We saw an issue with some of our servers were changing from Retired or In Use to 'Non-Operatonal' even though we do not use this status in our Prod environment. At first we thought discovery was updating the status but it was happened on a different date that discovery was updating the CI.

 

After a lot of digging we found an OOTB Business Rule called 'Cascade Operational Status to Server' which runs on the  Virtual Machine Instance [cmdb_ci_vm_instance] table. We wanted our server CI's status to trump the VMI's status so we disabled this BR and the problem is now resolved. 

0 Helpfuls
  • 1,497 Views
1 REPLY 1

scottl
Kilo Sage

‎04-30-2025 05:25 PM

Did you actually solve this outside of turning off a business rule? Because if the Status of a retired CI changes and comes "back into life", it will set the operational_status as "non-operational". 

If anyone knows more on WHY and WHERE it does this, that would be great detailing that here.  Because if a CI becomes active again, it makes zero sense to set it as non-operational.

0 Helpfuls