Project

Profile

Help

Issue #6511

Content which depends on the pulp2 repo content is not skipped when its repo is not migrated

Added by ttereshc 8 months ago. Updated 16 days ago.

Status:
NEW
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:
Sprint:
Quarter:

Description

Content (errata) which depend on a repository should be skipped at migration time if a repo is not migrated. It will be pre-migrated but not moved further if a repo it depends on is not a part of the migration plan.

FWIW, Katello is fine, they always migrate everything for a plugin. But it's very inconvenient for testing and development.

solution

at the time pulp2 content will start the migration, pulp2 repos will be migrated already. Content that depends on the repository, at the migration time should check whether pulp2 repo was already migrated, if the corresponding repo is not migrated, do not migrate this content and skip

History

#1 Updated by ttereshc 7 months ago

  • Priority changed from Normal to Low
  • Triaged changed from No to Yes

#2 Updated by ttereshc 6 months ago

  • Description updated (diff)
  • Priority changed from Low to Normal
  • Sprint set to Sprint 74

#3 Updated by ttereshc 6 months ago

  • Sprint/Milestone set to 0.2.0

#4 Updated by ipanova@redhat.com 6 months ago

at the time pulp2 content will start the migration, pulp2 repos will be migrated already. Content that depends on the repository, at the migration time should check whether pulp2 repo was already migrated, if the corresponding repo is not migrated, do not migrate this content and skip

#5 Updated by ttereshc 6 months ago

Thinking more about it, I realised that there is a reason I wrote skipped at migration time. It will be pre-migrated but not moved further in the description. Remember that we rely on the timestamp of migration to pre-migrate the content. If we skip the content at the pre-migration time, it will never be migrated. So I suggest to skip at migration time as it is written now.

#6 Updated by ipanova@redhat.com 6 months ago

  • Description updated (diff)

#7 Updated by rchan 6 months ago

  • Sprint changed from Sprint 74 to Sprint 75

#8 Updated by rchan 5 months ago

  • Sprint changed from Sprint 75 to Sprint 76

#9 Updated by rchan 5 months ago

  • Sprint changed from Sprint 76 to Sprint 77

#10 Updated by ttereshc 4 months ago

  • Description updated (diff)

#11 Updated by rchan 4 months ago

  • Sprint changed from Sprint 77 to Sprint 78

#12 Updated by ipanova@redhat.com 4 months ago

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

#13 Updated by rchan 4 months ago

  • Sprint changed from Sprint 78 to Sprint 79

#14 Updated by ttereshc 3 months ago

  • Sprint/Milestone deleted (0.2.0)

#15 Updated by rchan 3 months ago

  • Sprint changed from Sprint 79 to Sprint 80

#16 Updated by rchan 3 months ago

  • Sprint changed from Sprint 80 to Sprint 81

#17 Updated by rchan 2 months ago

  • Sprint changed from Sprint 81 to Sprint 82

#18 Updated by ipanova@redhat.com about 2 months ago

  • Sprint deleted (Sprint 82)

Taking off the sprint for now. If time permits will come back to this work in the upcoming sprint.

#19 Updated by ipanova@redhat.com 16 days ago

  • Status changed from ASSIGNED to NEW
  • Assignee deleted (ipanova@redhat.com)

Please register to edit this issue

Also available in: Atom PDF