Project

Profile

Help

Actions
Send by e-mail Copy link

Story #2575

closed

As a user, I don't have to wait for migration 0020_nested_drpm_directory if there are no DRPMs

Added by mhrivnak about 7 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
daviddavis
Sprint/Milestone:
-
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:

https://github.com/pulp/pulp_rpm/blob/pulp-rpm-2.12.0-1/plugins/pulp_rpm/plugins/migrations/0020_nested_drpm_directory.py

Actions
Send by e-mail Copy link

Also available in: Atom PDF