AWS discovery keeps on changing VMIs state from ON->Terminated->On

[Shreya Jain1]

We are facing issue where AWS discovery changes VMIs state from ON->Terminated->On and Install Status from Installed->Retired->Installed (refer attached screenshot)

Cloud team says they haven't terminated VM but on ServiceNow end its getting updated to Terminated. In single discovery execution, state/Install Status field gets updated to Terminated/Retired and after a few minutes it changes back to ON/Installed.

I checked discovery logs, VMs state shows ON in "Amazon AWS - Virtual Server (LP)" pattern logs, also I didn't find any pattern deletion strategy that could've caused this.

Did anyone come across similar behavior?

[Pravin13]

Thank you Shreya for your response. But in our case I am able to find only one input payload but has same issue. Not sure if you can but if possible can you paste the case number here? I have also opened up a case & want to provide that to Hi engineer for reference as engineer not able to find any previous case with this issue. 

[Shreya Jain1]

Hi Pravin, 

Did you get any solution on this?

Regards,
Shreya

[Pravin13]

Hi Shreya,

As per support issue is related to having multiple payloads where some of the payloads have the CI information and some do not which can also lead to key values missing. And they asked us to update the trigger rule as below.

We have tested this in lower environment & not seeing the flips so far. Hope this helps.

- Pravin

[Shreya Jain1]

Hi @Pravin13, 

Thank you for sharing this, do you know if ServiceNow raised PRB for this issue or if they published any KB article regarding this?

Regards,

Shreya

[Namrata8]

Hi Pravin, we also received this issue, solution for this issue is added into plugin update for discovery. so you can avoid customization if its not done.

Thanks