Hi,
We have vCenter Discovery running in our subProduction envs, vCenter credentials seem to be good and we are are successfully querying vCenter. There seems to be a hiccup with VMs that get deleted in so far as the VM Instance table is reflecting the state of the VM as Terminated but the [operational] status remains as Operational. The documentation for Discovery for VMware vCenter suggests that the status should be getting set to Retired. Do we need to build our own rule for just the vm instance table to change the status or should be be one OOB that may have gotten disabled when implemented. I can't believe that vCenter Event Colletor would need to be installed to do this.
Where this is problematic for us is that because the business rule for cascade the VM status to the server CI is looking at operational status, the server CI is essentially orphaned and left in the status 'operational', And having to manually retire the CI record.
Appreciate any help or suggestions.
