As a user, I can track the progress of pulp2->pulp3 migrations
Katello needs to be able to track the progress of migrations.
The primary requirements are:
- To know when the migration has completed
- To know how many Pulp 2 repositories have been migrated to Pulp 3
Other factors such as "how many distributions have been migrated" or "how many repository versions were created" are of far lesser importance.
Updated by dalley almost 4 years ago
As it currently stands, requirement #1 is fulfilled by Katello-side task group analysis. There are some unresolved concerns about edge cases:
What happens if the primary task in a task group, the one which spawns new tasks, fails or is cancelled before finalizing the task group?
Then you'd be in a situation where all_tasks_dispatched is forever False on the task group.
Should we handle this, and if so, how?
#2 is incomplete.
Updated by firstname.lastname@example.org over 3 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|52fc23c7d54348a0d26613e8482c3cdca38b016a.