Project

Profile

Help

Issue #6511

closed

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

Added by ttereshc almost 4 years ago. Updated almost 3 years ago.

Status:
CLOSED - WONTFIX
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

Actions #1

Updated by ttereshc almost 4 years ago

  • Priority changed from Normal to Low
  • Triaged changed from No to Yes
Actions #2

Updated by ttereshc almost 4 years ago

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

Updated by ttereshc almost 4 years ago

  • Sprint/Milestone set to 0.2.0
Actions #4

Updated by ipanova@redhat.com almost 4 years 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

Actions #5

Updated by ttereshc almost 4 years 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.

Actions #6

Updated by ipanova@redhat.com almost 4 years ago

  • Description updated (diff)
Actions #7

Updated by rchan almost 4 years ago

  • Sprint changed from Sprint 74 to Sprint 75
Actions #8

Updated by rchan almost 4 years ago

  • Sprint changed from Sprint 75 to Sprint 76
Actions #9

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 76 to Sprint 77
Actions #10

Updated by ttereshc over 3 years ago

  • Description updated (diff)
Actions #11

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 77 to Sprint 78
Actions #12

Updated by ipanova@redhat.com over 3 years ago

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

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 78 to Sprint 79
Actions #14

Updated by ttereshc over 3 years ago

  • Sprint/Milestone deleted (0.2.0)
Actions #15

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 79 to Sprint 80
Actions #16

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 80 to Sprint 81
Actions #17

Updated by rchan over 3 years ago

  • Sprint changed from Sprint 81 to Sprint 82
Actions #18

Updated by ipanova@redhat.com over 3 years ago

  • Sprint deleted (Sprint 82)

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

Actions #19

Updated by ipanova@redhat.com over 3 years ago

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

Updated by ttereshc almost 3 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Low priority at the moment, not on a roadmap. Please reopen if you are affected and it needs to be fixed.

Also available in: Atom PDF