Retired VMware VMs Operational Status remains as OperationalDescriptionServer's operational status behavior -Status of that VM is marked as Retired, but operational status is unchangedSteps to Reproduce 1. Discover a VMware cloud2. Notice cmdb_ci_vmware_instance record getting created.3. Retire a VM4. Trigger discovery again5. Status of that VM is marked as Retired, but operational status is unchanged.WorkaroundIn recent times there has been confusion related to values for various fields like Operational Status, Install Status & Hardware Status fields for CIs related to vCenter discovery like cmdb_ci_vm_instances, cmdb_ci_esx_servers, etc. As a part of the standard discovery process for vcenter we only set the install status fields and leave out the rest of the status fields this is by design. Since as a part of vcenter discovery we don't get any operational status for various CIs and customers also have their own views related to operational status for a CI so hence we have left it to the best knowledge of customers. Further hardware status fields are intended for HAM and also are not touched as part of vcenter discovery. This is expected behavior and by design in all currently supported releases.Related Problem: PRB1565922