Windows CI install status getting changed to 'Retired'

[Rohit7]

Hi All,

when performed the Quick discovery - CI's (cmdb_ci_win_server ) are getting discovered successfully with 'Installed'.

then after specific period of interval - It has been noticed that few of Windows CI are getting Retired after specific period of interval most probably on Sunday. when I tried to look out for by looking into scheduled Jobs /BR not able to find out from where exactly this status is getting changed to 'Retired'. at the same time respective asset is also in retired state which is as expected

So I am looking for what exactly happening in background which causing CI status getting changed to 'Retired '.Any inputs on the same will be helpful.

[Deepti Rajvansh]

Hi,

Please check any new deployment in the system:

1. look for the BR & client scripts running on cmdb_ci/cmdb_ci_server/cmdb_ci_win_server tables. 

2. Also, please check if you have asset associated to this & if the state has been changed to retire.

[Deepti Rajvansh]

Hi,

Please check for new deployment in the system:

1. Look for the BR & client scripts running on cmdb_ci/cmdb_ci_server/cmdb_ci_win_server tables. 

2. Also, please check if you have asset associated to this & if the state has been changed to retire.

Please mark my response correct/helpful as applicable!

[Rohit7]

Asset and CI both entries are getting Retired at same time when checked in audit log which is as expected . checking BR and client client does not help for 'install_status' field updating to Retired(value:7)

also when checked common pattern observed for CI's is status is getting updated to 'retired' on Sunday only so there is some background job running which are bringing status to 'Retired'. but on what basis its setting to retired  and which Job causing this ? when checked into jobs its not easier though to find out which one .

[Deepti Rajvansh]

Please check which jobs are running on Sunday. Then you may apply a filter for cmdb tables that will filter out jobs to investigate.