How does Discovery sets the hardware_status field on a Server CI

[chaluisant]

We have the hardware_status field exposed on the cmdb_ci_server form.  Every time Discovery runs it sets the field to "installed"  I am trying to understand where in the process that happens.  I don't see it in the corresponding pattern nor I see any business rule being triggered when discovery runs.  We are not creating assets for these servers.

[Prabu Velayutha]

If you have audit enabled in the server table, you can check the audit list and find the updated by user and time stamp, is that discovery user updated the value of this field?

[chaluisant]

Yes.  I see the mid_server user as the "updated by" field.  The challenge I have is that I see no business rule or script triggered at the time of the update.  

[chaluisant · Accepted solution]

We have identified the cause of this issue:

• As Discovery runs the OSs - Pre Sensor script is configured to set a server hardware_status to installed if the field is empty. (or in our case in an invalid state)

  

• OOB the choices for the  hardware_status come from the cmdb_ci_hardware state field and installed is the default value

• In our system, the choices for the  hardware_status were set by our Implementation Partner to come from alm_asset which does not include “installed”.  

Given these conditions, we now need to determine if we should:

1. Customize the script to set the hardware_status to “1” (In Use) OR
2. Normalize the hardware_status field to match how it is set OOB.