Project

Profile

Help

Issue #6186

Mutable content that has changed since the last migration run is not migrated

Added by ipanova@redhat.com over 1 year ago. Updated about 1 year ago.

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

Description

Docker Tag and Erratum are mutable types in pulp2.

  1. add to the migrator pulp2 mutable content types
  2. in pre-migration step, before saving Pulp2Content, filter out content that is mutable https://github.com/pulp/pulp-2to3-migration/blob/master/pulp_2to3_migration/app/pre_migration.py#L133
  3. The immutable content will use bulk_create
  4. Mutable content will be processed one by one and checked for incoming last_updated versus the one we have saved. Based on this the existing Pulp2Content with whether be deleted and created a new one or we'll catch and pass the integrity error
  5. Flip the is_migrated flag to False on all the repos that contain the updated mutable content

History

#1 Updated by ipanova@redhat.com over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ipanova@redhat.com
  • Sprint set to Sprint 66

#2 Updated by ttereshc over 1 year ago

  • Groomed changed from No to Yes

#3 Updated by rchan over 1 year ago

  • Sprint changed from Sprint 66 to Sprint 67

#4 Updated by ipanova@redhat.com over 1 year ago

  • Status changed from ASSIGNED to POST

#5 Updated by ipanova@redhat.com over 1 year ago

  • Status changed from POST to MODIFIED

#8 Updated by ttereshc about 1 year ago

  • Sprint/Milestone set to 0.1.0

#9 Updated by ttereshc about 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF