The state field is empty for the retired VMware VMs,rather it should be terminatedIssue: The state field is empty for the retired VMware VMs, rather it should be terminated. If a VM is deleted from the vCenter, Discovery marks the state as terminated whereas vCenter event collector marks the state as empty. Due to this, there is no uniformity in state. Steps to reproduce: 1. Create a VM in vCenter 2. Perform the vCenter discovery 3. A record is created for the VM in cmdb_ci_vmware_instance table 4. Delete the VM in the vCenter 5. Perform the vCenter discovery again 6. The status is marked as Retired and state is marked as terminated 1. Start the vCenter event collector 2. Create a VM in vCenter 3. A record is created for the VM in cmdb_ci_vmware_instance table by the event collector 4. Delete the VM in the vCenter 5. The status is marked as Retired and state is marked as empty by the event collector Fix: The fix here is to make the vCenter event collector mark the state as terminated for the deleted VMs to be on par with Discovery The issue is fixed in PRB1670415 in Washington DC For the existing records in cmdb_ci_vmware_instance where the status is Retired and state is empty, there is a scheduled job with name 'Mark VM state as terminated'. It is inactive by default. The customer can execute it and it will mark the state as terminated for the existing retired VMs. Once the task is complete, it will be marked as inactive automatically