Actions
Story #2575
closedAs a user, I don't have to wait for migration 0020_nested_drpm_directory if there are no DRPMs
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
2.13.0
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Easy Fix, Pulp 2
Sprint:
Sprint 15
Quarter:
Description
This migration walks the entire tree of published RPM repos looking for places to fix incorrectly published DRPMs. This can take a long time, especially on latent filesystems. If the migration checked the database for DRPMs first, it could skip that expensive process for users with no DRPMs.
I suggest a check here for whether the DB contains DRPMs:
Updated by semyers about 6 years ago
- Sprint/Milestone set to 33
- Groomed changed from No to Yes
Updated by daviddavis about 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to daviddavis
Added by daviddavis about 6 years ago
Updated by daviddavis about 6 years ago
- Status changed from ASSIGNED to POST
Updated by daviddavis about 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 9b85ad0c1fab218eced9be179700520ec97d4d89.
Updated by pcreech almost 6 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Skip the drpm migration if no drpms
fixes #2575 https://pulp.plan.io/issues/2575