VM Instance records are updated by discovery install Staus as "Retired" and Operational Status as 6

[Abhishek41]

Hi Experts,

We are on Utah version, and we are seeing that the VM instance records which are updated by discovery are showing install status for VM instances as "retired" and Operational status value as "6", which means in stock.

After checking with the infra team, they confirmed the VMs (Linux + Solaris mostly) are not retired but still in ServiceNow it is showing as retired and operational status value as "6".

Kindly help with the issue in case somebody has only encountered the same.

Thanks,

Abby

[SiD2]

Hi @Abhishek41 

Ideally, it shouldn't happen, have you modified the schedule by any chance so that those VMs aren't discovered in subsequent runs? If yes, it could be expected as discovery marks the items [retired or per del strategy] which were not discovered again but already exists in your CMDB.

Do you have cloud events enabled and for which cloud provider are you running discovery?

[Abhishek41]

Hi @SiD2

Discovery schedule is not modified for the VMs and AWS cloud event is also not enabled for the VMs. 

Also, the very strange part earlier the operational status for vm instance records were coming as operational or not operational but suddenly it is now coming as a numeric value "6" , which is in-stock.

Thanks,

Abby

[SiD2]

Hi@Abhishek41

That seems strange! Possibly some customization from your end or else I would suggest creating a support ticket with us to check in detail.

On the operational status, someone could have modified the definition of it, 6 is for Retired only OOB.

[Rashmika BS]

Has this been resolved?