Bug 1377418

Summary: db:migrate failure during upgrade from 3.2 to 4.1
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ApplianceAssignee: Nick Carboni <ncarboni>
Status: CLOSED ERRATA QA Contact: Jan Krocil <jkrocil>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: abellott, fahmed, gtanzill, jhardy, ncarboni, ngupta, obarenbo, simaishi, tachoi
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.3   
Hardware: x86_64   
OS: Linux   
Whiteboard: upgrade:migration
Fixed In Version: 5.6.3.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1375029 Environment:
Last Closed: 2016-11-30 19:54:28 UTC Type: ---
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: 1375029    
Bug Blocks:    

Comment 2 CFME Bot 2016-11-03 19:51:14 UTC 
New commit detected on ManageIQ/manageiq/darga:
https://github.com/ManageIQ/manageiq/commit/1c0211cf5a7298cbaade3d1603b4b93c21241721

commit 1c0211cf5a7298cbaade3d1603b4b93c21241721
Author:     Jason Frey <fryguy9>
AuthorDate: Wed Sep 14 14:53:02 2016 -0400
Commit:     Oleg Barenboim <chessbyte>
CommitDate: Thu Nov 3 15:50:00 2016 -0400

    Merge pull request #11197 from carbonin/remove_composite_key_migrations
    
    Remove composite primary key migration logic with no net effect
    (cherry picked from commit df3737f3cd4b9fe27184a44b4b82d5b1879f3aaf)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1377418

 ...19_add_composite_primary_keys_to_join_tables.rb | 33 ----------------------
 ...0406195810_add_id_primary_key_to_join_tables.rb | 29 -------------------
 ...95810_add_id_primary_key_to_join_tables_spec.rb | 10 -------
 3 files changed, 72 deletions(-)
 delete mode 100644 db/migrate/20160106214719_add_composite_primary_keys_to_join_tables.rb
Comment 8 errata-xmlrpc 2016-11-30 19:54:28 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/RHSA-2016-2839.html