Project

General

Profile

Refactor #15866

Provide alternative way of migrating data as oposed misuing db:migrate for this purpose

Added by Ivan Necas about 5 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DB migrations
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

In couple of years, we hit quite a lot issues that were related to the fact that we
perform data manipulation in db:migration. This issues include:

1. problems with relying on columns in data that were added at the same run
and not being populated yet

2. problems with external systems needed to be ready as part of the data migration

The issue becomes even more visible when the migrations are run with more plugins
installed.

The goal for this issue is to find a better way to organize our data migrations
that would prevent us from hitting the issues we did in the past.


Related issues

Related to Foreman - Bug #15655: [upgrade] db migrate failed with error: undefined local variable or method `openscap_proxy_id'Closed2016-07-12
Related to Foreman - Bug #15040: Could not find table 'users' during db:migrateClosed2016-05-13
Related to Foreman - Bug #14468: --foreman-unattended breaks db:migrateClosed2016-04-04
Related to Foreman - Bug #14410: Failure to run DB migrations prevents plugin permissions being loadedClosed2016-03-31
Related to Katello - Refactor #15200: db migrations should not be used to modify external databasesRejected2016-05-26
Related to Foreman - Bug #14983: Faking host and other models with STI in migrations doesn't work due to STINew2016-05-10
Related to Foreman - Bug #15920: migration CopyUnmanagedHostsToInterfaces may fail on interface conversations when ipv6 migration has not occurred Rejected2016-07-31

History

#1 Updated by Ivan Necas about 5 years ago

  • Related to Bug #15655: [upgrade] db migrate failed with error: undefined local variable or method `openscap_proxy_id' added

#2 Updated by Ivan Necas about 5 years ago

  • Related to Bug #15040: Could not find table 'users' during db:migrate added

#3 Updated by Ivan Necas about 5 years ago

  • Related to Bug #14468: --foreman-unattended breaks db:migrate added

#4 Updated by Ivan Necas about 5 years ago

  • Related to Bug #14410: Failure to run DB migrations prevents plugin permissions being loaded added

#5 Updated by Ivan Necas about 5 years ago

  • Related to Refactor #15200: db migrations should not be used to modify external databases added

#6 Updated by Ivan Necas about 5 years ago

I just did a simple search db DB migrate issues in redmine at added few that are a direct consequence
of the way we do the data migrations right now.

#7 Updated by Ivan Necas about 5 years ago

  • Related to Bug #14983: Faking host and other models with STI in migrations doesn't work due to STI added

#8 Updated by Ivan Necas about 5 years ago

Another example of consequences from the current way we do migrations https://bugzilla.redhat.com/show_bug.cgi?id=1360707

#9 Updated by Brad Buckingham about 5 years ago

  • Bugzilla link set to 1361676

#10 Updated by Marek Hulán about 5 years ago

  • Related to Bug #15920: migration CopyUnmanagedHostsToInterfaces may fail on interface conversations when ipv6 migration has not occurred added

Also available in: Atom PDF