Project

Profile

Help

Story #7714

As a user, I can start migration from scratch for a specified set of plugins

Added by ttereshc 6 months ago. Updated 4 months ago.

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

100%

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

Description

Motivation

In case of any major issues during migration, manual changes in the db (it's not supposed to happen but some people still do it), just willingness to start from scratch, there is no way to remove migrated data in pulp 3, apart from dropping database.

Proposed Solution

Provide a separate action to remove data for plugins specified in a Migration Plan
POST /pulp/api/v3/migration-plans/<uuid>/reset/

This action should not allow running any migration in parallel.
This action will remove all the data in Pulp 3 for the corresponding Pulp 2 plugins specified in the migration plan (even if the data is not migrated but was added later), all pre-migrated data, all content/artifacts/remoteartifacts, repositories, remotes, publications, distributions for those plugins (pulp2-> pulp3: iso -> file plugin, rpm -> rpm plugin, docker -> container plugin)

Associated revisions

Revision 8dc07971 View on GitHub
Added by ttereshc 5 months ago

Add a reset/ endpoint to be able to run migration from scratch.

closes #7714 https://pulp.plan.io/issues/7714

Revision 8dc07971 View on GitHub
Added by ttereshc 5 months ago

Add a reset/ endpoint to be able to run migration from scratch.

closes #7714 https://pulp.plan.io/issues/7714

Revision 8dc07971 View on GitHub
Added by ttereshc 5 months ago

Add a reset/ endpoint to be able to run migration from scratch.

closes #7714 https://pulp.plan.io/issues/7714

History

#1 Updated by ttereshc 6 months ago

  • Description updated (diff)

#2 Updated by ttereshc 6 months ago

  • Description updated (diff)

#3 Updated by ttereshc 6 months ago

  • Description updated (diff)

#4 Updated by ttereshc 6 months ago

  • Description updated (diff)

#5 Updated by jsherril@redhat.com 6 months ago

  • Tags Katello added

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

  • Groomed changed from No to Yes

#7 Updated by ttereshc 6 months ago

  • Sprint set to Sprint 84

#8 Updated by ttereshc 6 months ago

Just now, we have a bug because of which some RPM metadata was not migrated correctly. An ability to start migration from scratch would really help users here.

#9 Updated by ttereshc 6 months ago

  • Priority changed from Normal to High

#10 Updated by rchan 5 months ago

  • Sprint changed from Sprint 84 to Sprint 85

#11 Updated by ttereshc 5 months ago

  • Assignee set to ttereshc

#12 Updated by dalley 5 months ago

This action will remove all the data in Pulp 3 for the corresponding Pulp 2 plugins specified in the migration plan (even if the data is not migrated but was added later)

What about content units that may or may not have been migrated, but are shared with non-migrated, native Pulp 3 repositories?

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

dalley wrote:

This action will remove all the data in Pulp 3 for the corresponding Pulp 2 plugins specified in the migration plan (even if the data is not migrated but was added later)

What about content units that may or may not have been migrated, but are shared with non-migrated, native Pulp 3 repositories?

We are warning users that you are not supposed to use the plugin and then migrate data from pulp2 to 3 https://pulp-2to3-migration.readthedocs.io/en/latest/migration_plan.html

#14 Updated by ttereshc 5 months ago

+1
Also since we are not supporting mixed repositories and they are typed, we can't have a content shared with other plugin in other repositories other than plugin ones.

#15 Updated by ttereshc 5 months ago

  • Status changed from NEW to ASSIGNED

+1 Also since we are not supporting mixed repositories and they are typed, we can't have a content shared with other plugin in other repositories other than plugin ones.

#16 Updated by ttereshc 5 months ago

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

#17 Updated by ttereshc 4 months ago

  • Sprint/Milestone set to 0.6.0

#18 Updated by ttereshc 4 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF