Bug 1342586

Summary: Events portion of database bloats on migration of 5.4 to 5.5 (ems_events to event_streams)
Product: Red Hat CloudForms Management Engine Reporter: Lucy Fu <lufu>
Component: ApplianceAssignee: Lucy Fu <lufu>
Status: CLOSED ERRATA QA Contact: Alex Krzos <akrzos>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5.0CC: abellott, akrzos, cpelland, dajohnso, hhudgeon, jhardy, jprause, lbopf, lufu, obarenbo
Target Milestone: GAKeywords: ZStream
Target Release: 5.5.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: migration:database:event
Fixed In Version: 5.5.5.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1339303 Environment:
Last Closed: 2016-07-26 15:35:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1339303, 1342612    
Bug Blocks:    

Comment 2 CFME Bot 2016-06-03 17:17:37 UTC 
New commit detected on cfme/5.5.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=01b5ef6b1e7798c10690fba3db50b5aa0ef6d0e7

commit 01b5ef6b1e7798c10690fba3db50b5aa0ef6d0e7
Merge: 377b62a 0cc70a9
Author:     Greg McCullough <gmccullo>
AuthorDate: Fri Jun 3 13:14:27 2016 -0400
Commit:     Greg McCullough <gmccullo>
CommitDate: Fri Jun 3 13:14:27 2016 -0400

    Merge branch '5.5.z-migration_time_1339303' into '5.5.z'
    
    Changes to improve the migration time for EmsEvent -> EventStream.
    
    [Original PR](https://github.com/ManageIQ/manageiq/pull/9067) has two commits.
    Only one commit is appliable to 5.5.z.
    Clean cherry-pick.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1342586
    
    See merge request !957

 .../20150806211453_rename_ems_event_table_to_event_stream.rb     | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)
Comment 7 errata-xmlrpc 2016-07-26 15:35:17 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://rhn.redhat.com/errata/RHBA-2016-1488.html