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

Also available in: Atom PDF