Project

General

Profile

Actions
Copy link

Tracker #37076

open

make it possible to run seeds/migrations after foreman was fully migrated/seeded

Added by Evgeni Golov 10 months ago. Updated 10 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

75%

Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Rails executes migrations in order of their versions, regardless whether they come from core or from a plugin.
This works fine when you migrate/seed both in one go (= install both gems, run db actions), but not if you install Foreman first and then try to add Katello on top.
This issue is a tracker for all the existing bugs that need to be fixed in order to make it possible to perform Katello DB actions after Foreman has been fully installed.

Subtasks 4 (1 open — 3 closed)

Bug #37073: Migration error 'column settings.category does not exist'ClosedEvgeni GolovActions
Bug #37074: Migration error 'users.disabled' already existsClosedEvgeni GolovActions
Bug #37075: Invalid single-table inheritance type: ConfigManagementError is not a subclass of RemoveKatelloFromNotificationName::FakeMailNotificationClosedEvgeni GolovActions
Bug #37077: undefined method `repository_url' for nil:NilClassNewActions
Actions
Copy link
 #1

Updated by Evgeni Golov 10 months ago

  • Subtask #37075 added
Actions
Copy link
 #2

Updated by Evgeni Golov 10 months ago

  • Subtask #37074 added
Actions
Copy link
 #3

Updated by Evgeni Golov 10 months ago

  • Subtask #37073 added
Actions
Copy link
 #4

Updated by Evgeni Golov 10 months ago

  • Subtask #37077 added
Actions
Copy link
 #5

Updated by Partha Aji 10 months ago

  • Target version set to Katello 4.12.0
  • Triaged changed from No to Yes
Actions
Copy link
 #6

Updated by Partha Aji 10 months ago

  • Target version deleted (Katello 4.12.0)
Actions
Copy link

Also available in: Atom PDF