Project

Profile

Help

Story #7714

closed

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

Added by ttereshc about 2 years ago. Updated almost 2 years 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)

Actions #1

Updated by ttereshc about 2 years ago

  • Description updated (diff)
Actions #2

Updated by ttereshc about 2 years ago

  • Description updated (diff)
Actions #3

Updated by ttereshc about 2 years ago

  • Description updated (diff)
Actions #4

Updated by ttereshc about 2 years ago

  • Description updated (diff)
Actions #5

Updated by jsherril@redhat.com about 2 years ago

  • Tags Katello added
Actions #6

Updated by ipanova@redhat.com about 2 years ago

  • Groomed changed from No to Yes
Actions #7

Updated by ttereshc about 2 years ago

  • Sprint set to Sprint 84
Actions #8

Updated by ttereshc about 2 years 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.

Actions #9

Updated by ttereshc about 2 years ago

  • Priority changed from Normal to High
Actions #10

Updated by rchan about 2 years ago

  • Sprint changed from Sprint 84 to Sprint 85
Actions #11

Updated by ttereshc about 2 years ago

  • Assignee set to ttereshc
Actions #12

Updated by dalley about 2 years 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?

Actions #13

Updated by ipanova@redhat.com about 2 years 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

Actions #14

Updated by ttereshc about 2 years 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.

Actions #15

Updated by ttereshc about 2 years 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.

Added by ttereshc about 2 years ago

Revision 8dc07971

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

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

Added by ttereshc about 2 years ago

Revision 8dc07971

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

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

Added by ttereshc about 2 years ago

Revision 8dc07971

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

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

Actions #16

Updated by ttereshc about 2 years ago

  • Status changed from ASSIGNED to MODIFIED
  • % Done changed from 0 to 100
Actions #17

Updated by ttereshc almost 2 years ago

  • Sprint/Milestone set to 0.6.0
Actions #18

Updated by ttereshc almost 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF