Story #6769
closed
As a user, I can track the progress of pulp2->pulp3 migrations
Status:
CLOSED - CURRENTRELEASE
Description
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.
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.
- Blocked by Story #6858: As a user I can track progress of the task group with a task group progress report added
- Sprint/Milestone set to 0.2.0
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
- Groomed changed from No to Yes
- Sprint set to Sprint 75
- Sprint changed from Sprint 75 to Sprint 76
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
- Sprint/Milestone deleted (
0.2.0)
- Sprint/Milestone set to 0.3.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Add group progress report tracking during the migration.
Required PR: https://github.com/pulp/pulpcore/pull/755
closes #6769 https://pulp.plan.io/issues/6769