Issue #6511
closedContent which depends on the pulp2 repo content is not skipped when its repo is not migrated
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
Updated by ttereshc almost 4 years ago
- Priority changed from Normal to Low
- Triaged changed from No to Yes
Updated by ttereshc almost 4 years ago
- Description updated (diff)
- Priority changed from Low to Normal
- Sprint set to Sprint 74
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
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.
Updated by ipanova@redhat.com over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
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.
Updated by ipanova@redhat.com over 3 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
ipanova@redhat.com)
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.