Description of problem: ------------------------ The event_handling.tmpl.yml file contains this: AWS_EC2_Instance_CREATE: - policy: - src_vm - vm_create - refresh: - ems vm_create should be removed for the AWS_EC2_Instance_CREATE event and updated with the same basic comment to make clear why it is not provided as part of the configuration. See https://bugzilla.redhat.com/show_bug.cgi?id=1207865 for additional info. Version-Release number of selected component (if applicable): ------------------------ 5.4.0.0.24 How reproducible: ----------------- NA Steps to Reproduce: ------------------- 1. 2. 3. Actual results: --------------- Expected results: ----------------- Additional info: ----------------
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/42f61c707540f477ff8ebf1e7daac8cd57896389 commit 42f61c707540f477ff8ebf1e7daac8cd57896389 Author: Bill Wei <bilwei> AuthorDate: Mon May 4 17:49:53 2015 -0400 Commit: Bill Wei <bilwei> CommitDate: Mon May 4 17:52:23 2015 -0400 Fix AWS event mappings https://bugzilla.redhat.com/show_bug.cgi?id=1207865 vmdb/config/event_handling.tmpl.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
vm_create has been removed. ems refresh remains. Therefore when an instance is created it will still be added to VMDB. To verify you may need to wait for a few minutes because there could be a long delay before the event is received.
Verified that vm_create has been removed for AWS_EC2_instance_CREATE in the /var/www/miq/vmdb/config/event_handling.tmpl.yml file. AWS_EC2_Instance_CREATE: - refresh: - ems
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://rhn.redhat.com/errata/RHBA-2015-1100.html