Project

General

Profile

Refactor #15200

db migrations should not be used to modify external databases

Added by Ohad Levy about 6 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Branch:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

in katello 3.0 db migrations are used to modify pulp and candlepin databases.

IMHO this is the wrong approach which creates a lot of upgrades related issues (e.g. its enough one backend service malfunction and the entire upgrade is broken).

I think this should be redesigned, to use foreman-tasks or out side of the rails db migration process.

not to mention, so of the modifications do take a lot of time, and the ux experience on the installer is far from behind friendly (e.g. pulp migrations them self took more than 30 minutes on my system).


Related issues

Related to Foreman - Refactor #15866: Provide alternative way of migrating data as oposed misuing db:migrate for this purposeNew2016-07-27

History

#1 Updated by Eric Helms about 6 years ago

  • Legacy Backlogs Release (now unused) set to 143

#2 Updated by Justin Sherrill almost 6 years ago

  • Status changed from New to Rejected
  • Legacy Backlogs Release (now unused) changed from 143 to 166

We do avoid this when possible, but in this case the amount of changes needed was too dramatic and tables were going to be deleted in future migrations that contained needed data.

#3 Updated by Ivan Necas almost 6 years ago

  • Related to Refactor #15866: Provide alternative way of migrating data as oposed misuing db:migrate for this purpose added

Also available in: Atom PDF