How to restrict VM discovery CI record status change from Pending Retired to Installed

[karthiktammana]

Hi All, 

We have encountered a scenario that requires your expertise.

When a user requests a migration of a Virtual Machine (VM), we need to change its status from "Installed" to "Pending Retired." This status should remain until the old VM is decommissioned. During this period, the VM will be stopped or shut down but must still be accessible on the network (pingable).

Additionally, we need guidance on how to restrict the cloud discovery configuration item (CI) from automatically changing the status back from "Pending Retired" to "Installed," as this is currently happening out of the box.

Your insights on how to implement these changes would be greatly appreciated.

Thank you!

[Pratiksha]

Below is the logic on how the Operational Status is set on cmdb_ci_vm_instance by Cloud Discovery:
☞ If the VM state is on or off in the Cloud Provider (e.g. AWS, Azure), then the Operational Status is set to Operational.
(Default value of the Operational Status field)
☞ If the VM state is terminated, and the VM still exist in the Cloud Provider, then the Operational Status is set to Retired.
(By Business Rule "Retire/revive CI" on cmdb_ci_vm_instance)
☞ If the VM has been terminated, and has been cleaned up in the Cloud Provider, then the Operational Status is set to Non-Operational.