New commit detected on ManageIQ/manageiq-content/fine: https://github.com/ManageIQ/manageiq-content/commit/9729ab5bd8861f93784348f84e26c5ec8b0214b0 commit 9729ab5bd8861f93784348f84e26c5ec8b0214b0 Author: Greg McCullough <gmccullo> AuthorDate: Mon Jul 3 14:40:41 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Thu Jul 6 10:14:41 2017 -0400 Merge pull request #137 from bronaghs/aws_ebs_event_swithboard_support Event switchboard entries for Amazon EBS events. (cherry picked from commit df9c41a3de1bd0b3b6112db2339702218d228b11) https://bugzilla.redhat.com/show_bug.cgi?id=1468275 .../System/Event/EmsEvent/Amazon.class/attachvolume.yaml | 12 ++++++++++++ .../System/Event/EmsEvent/Amazon.class/copysnapshot.yaml | 12 ++++++++++++ .../System/Event/EmsEvent/Amazon.class/createsnapshot.yaml | 12 ++++++++++++ .../System/Event/EmsEvent/Amazon.class/createvolume.yaml | 12 ++++++++++++ .../System/Event/EmsEvent/Amazon.class/deletesnapshot.yaml | 12 ++++++++++++ .../System/Event/EmsEvent/Amazon.class/deletevolume.yaml | 12 ++++++++++++ 6 files changed, 72 insertions(+) create mode 100644 content/automate/ManageIQ/System/Event/EmsEvent/Amazon.class/attachvolume.yaml create mode 100644 content/automate/ManageIQ/System/Event/EmsEvent/Amazon.class/copysnapshot.yaml create mode 100644 content/automate/ManageIQ/System/Event/EmsEvent/Amazon.class/createsnapshot.yaml create mode 100644 content/automate/ManageIQ/System/Event/EmsEvent/Amazon.class/createvolume.yaml create mode 100644 content/automate/ManageIQ/System/Event/EmsEvent/Amazon.class/deletesnapshot.yaml create mode 100644 content/automate/ManageIQ/System/Event/EmsEvent/Amazon.class/deletevolume.yaml
https://github.com/ManageIQ/manageiq-content/pull/137 shows fine/backported. Moving to POST.
I have some issues with verifying this BZ: There are still events missing for Create volume and Detach volume. Shall I create new BZ for that? When I do something in AWS Console like adding a new snapshot or deleting a snapshot then refresh kicks off like in more than 30 minutes and that kick off can be triggered by something else.
Matous, Which events were you able to test? Thanks Bronagh
In terms of this one, I believe we can move to verified per the overall summary that ebs events are now trigger refreshes. With that said though, it sounds like we need to write an new BZ for the slowness of these events, is it completely on the AWS side and nothing we can do about it? Is it all AWS events or only specific ones like EBS (that I believe CloudWatch sends)?
Okay, only CloudWatch EBS Storage/Volume configuration is not working because of bug on the Amazon side. I was able to configure CloudTrail + CloudWatch with Ladas and it works now very well(Events are coming in < 5 minutes). Docs will be needed for this configuration. Verified in 5.8.1.5. Autorefresh worked with CreateVolume/AttachVolume/DeleteVolume and CreateSnapshot/CopySnapshot/DeleteSnapshot.
That great Matous. What is the bug on the AWS side? Can you review the doc text box in this BZ, is anything else needed?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1758