Bug 1537790

Summary: Event AWS_API_CALL_TerminateInstances on EC2 in wrong timeline category
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvidersAssignee: Julian Cheal <jcheal>
Status: CLOSED ERRATA QA Contact: thiebaut fischer <tfischer>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8.0CC: bsorota, cpelland, gblomqui, hkataria, izapolsk, jcheal, jfrey, jhardy, lavenel, mpovolny, obarenbo, smallamp, tfischer
Target Milestone: GA   
Target Release: 5.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.9.0.18 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1537165 Environment:
Last Closed: 2018-03-01 13:23:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: AWS Target Upstream Version:
Embargoed:
Bug Depends On: 1537165    
Bug Blocks:    

Comment 2 CFME Bot 2018-01-23 21:45:14 UTC 
New commit detected on ManageIQ/manageiq-providers-amazon/gaprindashvili:
https://github.com/ManageIQ/manageiq-providers-amazon/commit/0d35c0addfb41d0c22a7a2d4c6963c6885830643

commit 0d35c0addfb41d0c22a7a2d4c6963c6885830643
Author:     Bronagh Sorota <bsorota>
AuthorDate: Tue Jan 23 16:19:29 2018 -0500
Commit:     Satoe Imaishi <simaishi>
CommitDate: Tue Jan 23 16:36:17 2018 -0500

    Merge pull request #402 from juliancheal/deletion_events
    
    Moved AWS_API_CALL_TerminateInstances from addition to deletion category
    (cherry picked from commit 1dc1215536b726ece28c8f04db06932f58321b7a)
    
    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1537790

 config/settings.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
Comment 3 thiebaut fischer 2018-02-12 09:17:04 UTC 
Issue no more present on 5.9, but I found it as well on 5.8. is it possible to du plicate the bug to fix it on the other version?
Comment 8 errata-xmlrpc 2018-03-01 13:23:59 UTC 
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-2018:0380