Project

Profile

Help

Story #6769

As a user, I can track the progress of pulp2->pulp3 migrations

Added by dalley 6 months ago. Updated about 2 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 76
Quarter:

Description

Katello needs to be able to track the progress of migrations.

The primary requirements are:

  1. To know when the migration has completed
  2. 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.


Related issues

Blocked by Pulp - Story #6858: As a user I can track progress of the task group with a task group progress reportCLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 52fc23c7 View on GitHub
Added by ipanova@redhat.com 5 months ago

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

Revision 52fc23c7 View on GitHub
Added by ipanova@redhat.com 5 months ago

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

Revision 52fc23c7 View on GitHub
Added by ipanova@redhat.com 5 months ago

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

History

#1 Updated by dalley 6 months 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.

#2 Updated by ipanova@redhat.com 6 months ago

  • Blocked by Story #6858: As a user I can track progress of the task group with a task group progress report added

#3 Updated by ttereshc 6 months ago

  • Sprint/Milestone set to 0.2.0

#4 Updated by ttereshc 5 months ago

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

#5 Updated by ipanova@redhat.com 5 months ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 75

#6 Updated by rchan 5 months ago

  • Sprint changed from Sprint 75 to Sprint 76

#7 Updated by ipanova@redhat.com 5 months ago

  • Status changed from ASSIGNED to MODIFIED
  • % Done changed from 0 to 100

#9 Updated by ttereshc 3 months ago

  • Sprint/Milestone deleted (0.2.0)

#10 Updated by ttereshc 3 months ago

  • Sprint/Milestone set to 0.3.0

#11 Updated by ttereshc about 2 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF