Project

Profile

Help

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.

Added by ttereshc over 3 years ago. Updated about 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 88
Quarter:

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

Related to Pulp - Issue #8044: no index for _last_updated on content models causes a fatal error when ordered result is queriedCLOSED - CURRENTRELEASEggaineyActions

Also available in: Atom PDF