AWS_EC2_Instance_DELETE events are not always received about manageiq-providers-amazon HOT 8 CLOSED

@john-dupuy That should work.

from manageiq-providers-amazon.

@john-dupuy Can you show me your settings for aws event handling? I just want to make sure there's nothing unusual there.

from manageiq-providers-amazon.

@djberg96 I haven't touched the defaults for the ems_amazon config in the advanced settings yaml:

  :ems_amazon:
    :event_handling:
      :event_groups:
        :addition:
          :critical:
          - AWS_EC2_Instance_CREATE
          - AWS_API_CALL_RunInstances
          - AWS_API_CALL_CreateTags
        :update:
          :critical:
          - AWS_EC2_Instance_UPDATE
        :deletion:
          :critical:
          - AWS_EC2_Instance_DELETE
          - AWS_API_CALL_TerminateInstances
        :power:
          :critical:
          - AWS_EC2_Instance_running
          - AWS_EC2_Instance_shutting-down
          - AWS_EC2_Instance_stopped
          - EC2_Instance_State_change_Notification_running
          - EC2_Instance_State_change_Notification_shutting_down
          - EC2_Instance_State_change_Notification_stopped
          - EC2_Instance_State_change_Notification_stopping
          - EC2_Instance_State_change_Notification_terminated
          - EC2_Instance_State_change_Notification_pending
          - AWS_API_CALL_StopInstances
          - AWS_API_CALL_StartInstances

from manageiq-providers-amazon.

Not sure it's significant, but I think it was first added here: https://bugzilla.redhat.com/show_bug.cgi?id=1207865

from manageiq-providers-amazon.

@john-dupuy Can you test against master? I want to see if #633 made any difference. I'll do some testing on my end, too.

from manageiq-providers-amazon.

@djberg96 I don't have a way to test against master but I can pull the latest downstream appliance and apply the change that #633 brought in and test with that. Would that be enough?

from manageiq-providers-amazon.

As per our discussions offline, I am not able to replicate this. I tried termination via the console, the app, and a standalone script. In all cases I received two events per termination - AWS_API_CALL_TerminateInstances (start of termination) followed a couple minutes later by AWS_EC2_Instance_DELETE (termination complete).

At this point we're not sure if it's a 5.11 vs master issue or if it's something to do with the way the test case is setup. Still investigating...

from manageiq-providers-amazon.

After some more investigation it looks like this was a case of our EC2 instance being misconfigured. I (loosely) followed the steps outlined https://www.manageiq.org/docs/guides/providers/amazon_aws_config and got this working again.

EC2 has changed quite a bit since those docs were written, but the basic idea of them is still correct. After Step 3, I had to create a Rule under the CloudWatch Events to send them to the SNS Topic.

from manageiq-providers-amazon.