Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1214314 - Can't migrate clean Satellite 6.1 database
Summary: Can't migrate clean Satellite 6.1 database
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 1192329
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-22 12:22 UTC by Lukas Zapletal
Modified: 2017-02-23 20:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:55:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lukas Zapletal 2015-04-22 12:22:11 UTC 
TRIAGE NOTES: This bug is not against 6.1 Beta production, but against our internal git version (branch SATELLITE-6.1.0). It looks like a file was mis-commited, we need to fix this for GA.

Description of problem:

This migration was commited twice into the internal git repo:

db/migrate/20141225073211_add_description_to_taxonomies.rb
1:class AddDescriptionToTaxonomies < ActiveRecord::Migration

db/migrate/20150304140348_add_description_to_taxonomies.rb
1:class AddDescriptionToTaxonomies < ActiveRecord::Migration

Causing:

ActiveRecord::DuplicateMigrationNameError: Multiple migrations have the name AddDescriptionToTaxonomies

Blocking Satellite 6.1 from installation. This NOT made it in 6.1 beta.

The two commits creating those files are:

commit 554afdcb33c04d82d2fd254a3e8a57f480f38bf8
Refs: foreman-1.7.2.8-1-sat-1-g554afdc
Author:     Ori Rabin <orabin>
AuthorDate: Wed Mar 4 16:12:57 2015 +0200
Commit:     Ori Rabin <orabin>
CommitDate: Wed Mar 4 16:23:49 2015 +0200

Refs Bz#1192329 - description for organization moved to foreman

And:

Refs: foreman-1.7.2.15-1-sat-17-g17f6361
Author:     Ori Rabin <orabin>
AuthorDate: Thu Dec 25 11:18:30 2014 +0200
Commit:     Bryan Kearney <bkearney>
CommitDate: Thu Apr 16 13:07:31 2015 -0400

    Fixes #8764 - adds description to taxonomies

    (cherry picked from commit 581d3b6b36f5f4ec1251ae4ebbf4964843d2d3bb)

    Conflicts:
        app/views/taxonomies/_form.html.erb
Comment 1 RHEL Program Management 2015-04-22 12:23:15 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 2 Lukas Zapletal 2015-04-22 12:24:11 UTC 
This is blocking me from doing a demo, triaging and fixing :-)
Comment 6 Lukas Zapletal 2015-05-11 08:26:44 UTC 
Yes, thanks. This was fixed in the first compose.
Comment 7 Bryan Kearney 2015-08-11 13:18:53 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 8 Bryan Kearney 2015-08-12 13:55:35 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.