Actions
Bug #31654
closed
support migration 'reset'
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Description
We should support a 'reset migration command' where:
we trigger: https://pulp-2to3-migration.readthedocs.io/en/latest/restapi.html#operation/migration_plans_reset
we delete all the pulp3 href's on content units, and repository pulp3 hrefs, and pulp3 models (Katello::Pulp3::Distribution, Katello::Pulp3::Repositroy) within the katello db
This would start allow a user to start it from scratch. This would involve a rake task and a foreman-maintain command
This should error if we detect that content types have already been switched over.
Updated by Chris Roberts about 3 years ago
- Target version set to Katello 3.18.2
- Triaged changed from No to Yes
Updated by The Foreman Bot about 3 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ian Ballou
- Pull request https://github.com/Katello/katello/pull/9142 added
Updated by Ian Ballou about 3 years ago
3.18 needs the updated pulp 2 to 3 migration client gem for reset to work. This upgrade can probably happen when the reset commit is cherry-picked to 3.18.
Updated by Justin Sherrill about 3 years ago
- Has duplicate Bug #31336: support pulp3 migration reset flag to let users 'restart' from scratch added
Updated by Ian Ballou about 3 years ago
- Status changed from Ready For Testing to Closed
Fixed in the KATELLO-3.18 branch.
Actions