Issue #9387: Depsolving computes repoclosure once per-rpm being copied - RPM Support - Pulp

Actions

Send by e-mail Copy link

Issue #9387

closed

Depsolving computes repoclosure once per-rpm being copied

Added by ggainey about 3 years ago. Updated about 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Urgent

Assignee:

ggainey

Sprint/Milestone:

3.16.0

Start date:

Due date:

Estimated time:

Severity:

3. High

Version:

Platform Release:

OS:

Triaged:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 105

Quarter:

Description

Unlike Pulp2, Pulp3 on-copy depsolving is computing repoclosure on the destination repo once per RPM copied . It only takes 1s to compute - but when copying 10K rpms, that adds up, in both CPU and memory.

Related issues

Actions

Copy link

Updated by ggainey about 3 years ago

The reason this is happening is that we addressed https://pulp.plan.io/issues/6820. My contention is tha the bahvior called out by 6820 is in fact correct. On copy, what we try to insure is repoclosure for yum/dnf's sake - if you issue "dnf install foo" should result in the latest version of foo being installed.

Note that Pulp2 depsolving code currently also only does repo-closure on the final repo - see https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/importers/yum/pulp_solv.py#L987-L990

Actions

Copy link