Task #8314
closedMake migration no-op if there are no changes in plan and everything is migrated
100%
Description
Motivation¶
With improvements introduced earlier, the migration re-runs are much faster now, at he same time when no changes are made and everything is migrated, it can take a significant amount of time to re-run a migration which is supposed to be no-op. It is mostly noticeable on the large systems with many repositories in Pulp 2.
Suggested solution¶
- compare the previous and current plans
- allow pre-migration to run to check for any changes in pulp2 (not sure if there any shortcuts available there)
- if the plan is the same and everything has been migrated, finish the task and do not proceed with content migration or repo version creation.
Updated by ttereshc over 3 years ago
it's not very critical if we do it later than early March'21, but it would be really good to have it done now.
Updated by ipanova@redhat.com over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
Added by ipanova@redhat.com over 3 years ago
Added by ipanova@redhat.com over 3 years ago
Revision 9df621c0 | View on GitHub
Optimize tasks creations.
https://pulp.plan.io/issues/7009 https://pulp.plan.io/issues/8314
Added by ipanova@redhat.com over 3 years ago
Revision 9df621c0 | View on GitHub
Optimize tasks creations.
https://pulp.plan.io/issues/7009 https://pulp.plan.io/issues/8314
Updated by ipanova@redhat.com over 3 years ago
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|9df621c04e1f825ef57b21f7c114f98f76b2e5b1.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Optimize tasks creations.
closes #7009 closes #8314
https://pulp.plan.io/issues/7009 https://pulp.plan.io/issues/8314