Project

General

Profile

Actions

Bug #37073

closed

Tracker #37076: make it possible to run seeds/migrations after foreman was fully migrated/seeded

Migration error 'column settings.category does not exist'

Added by Evgeni Golov 9 months ago. Updated 8 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

See:

Part of this was fixed in #36007, but the old migration from 2016 was forgotten.
It's not an issue when you migrate foreman and katello in one go (as then Rails sorts the migrations in a way that the Katello one comes before the Foreman one that drops the category column), but is a problem when you try to install Katello ontop of Foreman.


Related issues 1 (0 open1 closed)

Related to Katello - Bug #36007: Migration error 'column settings.category does not exist'ClosedLeos StejskalActions
Actions #1

Updated by The Foreman Bot 9 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/10852 added
Actions #2

Updated by Evgeni Golov 9 months ago

  • Related to Bug #36007: Migration error 'column settings.category does not exist' added
Actions #3

Updated by Evgeni Golov 9 months ago

  • Parent task set to #37076
Actions #4

Updated by The Foreman Bot 8 months ago

  • Fixed in Releases Katello 4.12.0 added
Actions #5

Updated by Evgeni Golov 8 months ago

  • Status changed from Ready For Testing to Closed
Actions #6

Updated by Partha Aji 8 months ago

  • Target version set to Katello 4.12.0
  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF