Issue #7781
closed
In case of any issues in the middle of pre-migration, migration re-run doesn't pick up all the needed content.
Description
If I cancel a task at pre-migration stage or if there is a failure at pre-migration time, the next migration re-run won't continue properly. It will skip content based on its last_updated timestamp.
We need to pre-migrate content ordered by last_updated date to avoid this.
Related issues
Updated by ggainey almost 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ggainey
- Sprint set to Sprint 87
Updated by ttereshc almost 4 years ago
- Related to Issue #8044: no index for _last_updated on content models causes a fatal error when ordered result is queried added
Updated by ggainey almost 4 years ago
- Status changed from ASSIGNED to POST
Added by ggainey almost 4 years ago
Added by ggainey almost 4 years ago
Revision cfec44af | View on GitHub
Taught content pre_migration to use consistent ordering.
This allows retries after migration-failures to pick up from failure-points consistently.
NOTE: In the presence of large migrations, this code requires the index from https://github.com/pulp/pulp/pull/4011 to exist in Pulp2, or the migration is likely to fail at the order-by point.
fixes #7781
Added by ggainey almost 4 years ago
Revision cfec44af | View on GitHub
Taught content pre_migration to use consistent ordering.
This allows retries after migration-failures to pick up from failure-points consistently.
NOTE: In the presence of large migrations, this code requires the index from https://github.com/pulp/pulp/pull/4011 to exist in Pulp2, or the migration is likely to fail at the order-by point.
fixes #7781
Updated by ggainey almost 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulp:pulp-2to3-migration|cfec44afef40ac844ca64c45e5f115ce30a5f8df.
Updated by pulpbot almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Taught content pre_migration to use consistent ordering.
This allows retries after migration-failures to pick up from failure-points consistently.
NOTE: In the presence of large migrations, this code requires the index from https://github.com/pulp/pulp/pull/4011 to exist in Pulp2, or the migration is likely to fail at the order-by point.
fixes #7781