Actions
Backport #9296
closedBackport "After migration interruption, incomplete publications are not fixed after a re-run" to 0.11
Start date:
Due date:
% Done:
100%
Estimated time:
Triaged:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
To reproduce:
- interrupt migration at the moment when a publication is created but not completed (good luck)
- re-run migration and observe that pulp2repositories endpoint refers to incomplete publications. If you try to access them via content app, you'll get 404.
Related issues
Updated by ttereshc over 3 years ago
- Copied from Issue #9295: After migration interruption, incomplete publications are not fixed after a re-run added
Added by ttereshc over 3 years ago
Added by ttereshc over 3 years ago
Revision a474a325 | View on GitHub
Use only complete publication so remigration knows if a new publication is needed.
backports #9295 https://pulp.plan.io/issues/9295
fixes #9296
(cherry picked from commit 2694fa503928af5720417bb3e8afdea54c863183)
Added by ttereshc over 3 years ago
Revision a474a325 | View on GitHub
Use only complete publication so remigration knows if a new publication is needed.
backports #9295 https://pulp.plan.io/issues/9295
fixes #9296
(cherry picked from commit 2694fa503928af5720417bb3e8afdea54c863183)
Updated by ttereshc over 3 years ago
- Status changed from NEW to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|a474a3257d0e09304b236a8c5a3f6be0419c6420.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Use only complete publication so remigration knows if a new publication is needed.
backports #9295 https://pulp.plan.io/issues/9295
fixes #9296
(cherry picked from commit 2694fa503928af5720417bb3e8afdea54c863183)