Project

General

Profile

Actions

Refactor #15866

open

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

Added by Ivan Necas almost 8 years ago. Updated about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DB migrations
Target version:
-
Difficulty:
Triaged:
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 7 (1 open6 closed)

Related to Foreman - Bug #15655: [upgrade] db migrate failed with error: undefined local variable or method `openscap_proxy_id'ClosedShlomi Zadok07/12/2016Actions
Related to Foreman - Bug #15040: Could not find table 'users' during db:migrateClosedDominic Cleal05/13/2016Actions
Related to Foreman - Bug #14468: --foreman-unattended breaks db:migrateClosedOri Rabin04/04/2016Actions
Related to Foreman - Bug #14410: Failure to run DB migrations prevents plugin permissions being loadedClosedDaniel Lobato Garcia03/31/2016Actions
Related to Katello - Refactor #15200: db migrations should not be used to modify external databasesRejected05/26/2016Actions
Related to Foreman - Bug #14983: Faking host and other models with STI in migrations doesn't work due to STINew05/10/2016Actions
Related to Foreman - Bug #15920: migration CopyUnmanagedHostsToInterfaces may fail on interface conversations when ipv6 migration has not occurred Rejected07/31/2016Actions
Actions

Also available in: Atom PDF