Bug 1673848
| Summary: | AWS_EC2 events are not received by CloudForms | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Niladri Roy <niroy> | ||||||||
| Component: | Providers | Assignee: | Alexander Zagaynov <azagayno> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Matouš Mojžíš <mmojzis> | ||||||||
| Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> | ||||||||
| Priority: | high | ||||||||||
| Version: | 5.9.5 | CC: | azagayno, bsorota, dmetzger, jfrey, jhardy, jocarter, jprause, niroy, obarenbo | ||||||||
| Target Milestone: | GA | Keywords: | Reopened | ||||||||
| Target Release: | 5.10.2 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-03-20 12:21:42 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | Bug | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | AWS | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1679295 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 1528018 [details]
reproducer instance stop
Created attachment 1528019 [details]
reproducer instance start
Created attachment 1528020 [details]
reproducer instance terminate
> - AWS_EC2_* and EC2_Instance_State_change_Notification_* events are created > by AWS Config service ? Yes, here: https://github.com/ManageIQ/manageiq-providers-amazon/blob/068c4eb30e38580cdbe8a706d1310ef9f7613bda/app/models/manageiq/providers/amazon/cloud_manager/event_catcher/stream.rb#L243-L266 > * Then why do we only see the AWS_API_CALL_* events in the evm.log file? Try to set log level to "debug" and look for "Parsed event from SNS Message not recognized" string. https://github.com/ManageIQ/manageiq-providers-amazon/blob/068c4eb30e38580cdbe8a706d1310ef9f7613bda/app/models/manageiq/providers/amazon/cloud_manager/event_catcher/stream.rb#L198 > has created a new cloudwatch rule for the EC2 state change and in their logs we can see incoming EC2_Instance_State_change_Notification_* events > * Is this extra step a necessary step? it is not mentioned in our documentation Not sure, but should be not. I'll check. > - We see the below error in the logs for which this seems to be the solution > [https://access.redhat.com/solutions/2532401] > * Is this error in any way related for not receiving AWS_EC2_* events? No, it's not about this. You can also see a brief description of how it works here: https://github.com/ManageIQ/manageiq-providers-amazon/blob/068c4eb30e38580cdbe8a706d1310ef9f7613bda/app/models/manageiq/providers/amazon/cloud_manager/event_catcher/stream.rb#L2-L7 Hello Alex, Thanks for you reply. I have forwarded your suggestion to our customer. I'll wait for their reply with new logs. Meanwhile, I enabled debug logging in my reproducer environment and I could see the AWS_EC2_* events this time. These events came in after 2-3 minutes of the AWS_API_CALL events. [----] I, [2019-02-12T12:49:10.030730 #1286:a8c8c0] INFO -- : MIQ(ManageIQ::Providers::Amazon::CloudManager::EventCatcher::Stream#) Found SNS Message with message type AWS_EC2_Instance_stopped coming from [----] I, [2019-02-12T12:49:10.030851 #1286:a8c8c0] INFO -- : MIQ(ManageIQ::Providers::Amazon::CloudManager::EventCatcher::Stream#) Parsed event from SNS Message AWS_EC2_Instance_stopped coming from So I'm not sure what the issue is, as if you see customer logs, the AWS_EC2 events are not present. Additionally, when I reported the BZ, that time too the AWS_EC2 events were not seen in my reproducer environment. I also turned off debug logging and tested, I still see the AWS_EC2 events. Hi Niladri, do you have any updates? No update from Cu, I'm following up Got it, thank you! I'm lowering priority now, as it seems that it happened accidentally, and not reproducible. Feel free to change it back if I'm wrong. Since there was no updates for more than a week, I'm going to close current BZ tomorrow. Removing from 5.10.2 per input from CEE. Not reproducible and lack of response from customer. Previous comment / change was meant for a different ticket, putting back in 5.10.2 appropriate disposition. |
Description of problem: After adding AWS provider, we do receive events with Type like event_type=>AWS_API_* eg. "AWS_API_CALL_RunInstances", But we do not get any events like event_type=>AWS_EC2_* eg. "AWS_EC2_Instance_Running". Version-Release number of selected component (if applicable): 5.9.5 How reproducible: Always Steps to Reproduce: 1. Add AWS Provider 2. Enable AWS provider to send events to CloudForms ("4.3.6. Enabling Amazon EC2 Events " : https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html-single/managing_providers/#amazon-provider-aws-events) 3. Provision a new instance in AWS (not from CloudForms) 4. Power off the instance, observe the incoming events in evm.log 5. Power on the instance, observe the events 6. Terminate the instance Actual results: AWS_EC2_* are not seen in evm.logs Expected results: CloudForms should get AWS_EC2_* events Additional info: 1. Attaching the log excerpt files of my reproducer environment 2. I don't see the EC2_Instance_State_change_Notification_* events as well 3. My customer has been able to get the EC2_Instance_State_change_Notification_* events by the below workaround " A new CloudWatch rule will be defined to stream all the EC2 configuration update events to the AWSConfig_topic. "