Issue #7781: In case of any issues in the middle of pre-migration, migration re-run doesn't pick up all the needed content. - Migration Plugin - Pulp

Agile board
Agile charts

Agile boards

Pulp 2 QE Agile Board
Pulp 2 QE Agile Board - Priority View
Pulp 3 QE Agile Board
Pulp 3 RPM Tests Agile Board
Sprint 112 Agile Board

Custom queries

[All Projects] All Test Trackers
2.21.4 - Next Bugfix Release
2.21.4 MODIFIED
2.21.5
3.14.3
Easy Fix
FIPS open
Functional Tests
Galaxy NG
Groomed
Issues for Triage
Katello Integration
Next Docs Day
POST/ASSIGNED - no Sprint - Pulp2
POST/ASSIGNED - no Sprint - Pulp3
Prioritized Bugs
Pulp 3 Docs issues
Pulp2 issues available for next release
SELinux related
Sprint 111
Sprint 112
Sprint Candidates (also groomed)
Un-Triaged Bugs
Verification Required

Actions

Send by e-mail Copy link

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 about 4 years ago. Updated almost 4 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

ggainey

Sprint/Milestone:

0.7.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

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 queried

CLOSED - CURRENTRELEASE

ggainey

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by ttereshc about 4 years ago

Triaged changed from No to Yes

Actions

Copy link

Updated by ttereshc about 4 years ago

Tags Katello added

Actions

Copy link

Updated by ggainey almost 4 years ago

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

Actions

Copy link

Updated by rchan almost 4 years ago

Sprint changed from Sprint 87 to Sprint 88

Actions

Copy link

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

Actions

Copy link

Updated by ggainey almost 4 years ago

Status changed from ASSIGNED to POST

https://github.com/pulp/pulp-2to3-migration/pull/291

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

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

Actions

Copy link