Project

Profile

Help

Issue #7781

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 5 months ago. Updated 2 months 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 - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision cfec44af View on GitHub
Added by ggainey 3 months ago

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

Revision cfec44af View on GitHub
Added by ggainey 3 months ago

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

Revision cfec44af View on GitHub
Added by ggainey 3 months ago

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

History

#1 Updated by ttereshc 5 months ago

  • Triaged changed from No to Yes

#2 Updated by ttereshc 5 months ago

  • Tags Katello added

#3 Updated by ggainey 4 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ggainey
  • Sprint set to Sprint 87

#4 Updated by rchan 4 months ago

  • Sprint changed from Sprint 87 to Sprint 88

#5 Updated by ttereshc 3 months ago

  • Related to Issue #8044: no index for _last_updated on content models causes a fatal error when ordered result is queried added

#7 Updated by ggainey 3 months ago

  • Status changed from ASSIGNED to POST

#8 Updated by ggainey 3 months ago

  • Status changed from POST to MODIFIED

#9 Updated by ttereshc 3 months ago

  • Sprint/Milestone set to 0.7.0

#10 Updated by pulpbot 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF