Story #7714
closed
As a user, I can start migration from scratch for a specified set of plugins
100%
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)
Updated by ttereshc about 4 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.
Updated by dalley about 4 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?
Updated by ipanova@redhat.com about 4 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
Updated by ttereshc about 4 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.
Updated by ttereshc about 4 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 4 years ago
Added by ttereshc about 4 years ago
Revision 8dc07971 | View on GitHub
Add a reset/ endpoint to be able to run migration from scratch.
Added by ttereshc about 4 years ago
Revision 8dc07971 | View on GitHub
Add a reset/ endpoint to be able to run migration from scratch.
Updated by ttereshc about 4 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|8dc07971271258a43cb247acaa251669e55bddc0.
Updated by ttereshc almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Add a reset/ endpoint to be able to run migration from scratch.
closes #7714 https://pulp.plan.io/issues/7714