Project

Profile

Help

Story #7714

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

Added by ttereshc 5 days ago. Updated 5 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 84
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)

History

#1 Updated by ttereshc 5 days ago

  • Description updated (diff)

#2 Updated by ttereshc 5 days ago

  • Description updated (diff)

#3 Updated by ttereshc 5 days ago

  • Description updated (diff)

#4 Updated by ttereshc 5 days ago

  • Description updated (diff)

#5 Updated by jsherril@redhat.com 5 days ago

  • Tags Katello added

#6 Updated by ipanova@redhat.com 5 days ago

  • Groomed changed from No to Yes

#7 Updated by ttereshc 5 days ago

  • Sprint set to Sprint 84

Please register to edit this issue

Also available in: Atom PDF