Server CI's Operational Status is being updated to "6" again and again

[srikanthnelapud]

Overview

When users receive notification (for example, from vCenter, AWS, etc.) that a VM has been deprovisioned, the corresponding CI is marked in such a way as to remove it from subsequent daily license counts. However, when that VM is linked to a Server CI (of the type cmdb_ci_server or subordinate), that CI is not similarly marked. This causes the daily license count to not be reduced.

The deprovisioned status needs to be carried through to the linked Server CI in order to properly reduce the subsequent daily counts and this need is fulfilled by the business rule - "Cascade deprovisioned status to Server", introduced in "Paris" and later backported to "Orlando Patch 6" & "New York Patch 10".

Issue

This Business Rule is kicked off whenever there is an update in the "cmdb_ci_vm_instance" table and whose current.operational status == 6, thus updating the Server CI as well so no matter how many time the same CI in the VM instance table is updated, that many number of times the Server CI is updated as well thus resulting in frequent audit logs of Operational Status value being modified from 1 to 6.

Root Cause

The major root cause observed in most of the customer environments is the defaults for the Operational_status and install_status is set to something else rather than 1.

EXPECTED (SCREENSHOT): Defaults Data.png

For VMWare, we shouldn't update the retired CIs (VM Instance) install_status, again and again, so the respective fix has been already made in Quebec already (PRB1432885). 

Workarounds

1. Change the attached screenshot and update the defaults accordingly.
2. Change the business rule condition as below

(current.operational_status == 6) && (previous.operational_status != current.operational_status)