Actions
Bug #37073
closedTracker #37076: make it possible to run seeds/migrations after foreman was fully migrated/seeded
Migration error 'column settings.category does not exist'
Description
See:
- https://github.com/theforeman/foreman/pull/9524
- https://github.com/theforeman/foreman/pull/9524#issuecomment-1404661119
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.
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
Updated by Evgeni Golov 9 months ago
- Related to Bug #36007: Migration error 'column settings.category does not exist' added
Updated by Evgeni Golov 8 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|3773276af1e5489641132b60f455047b2d7f347f.
Updated by Partha Aji 8 months ago
- Target version set to Katello 4.12.0
- Triaged changed from No to Yes
Actions