Project

Profile

Help

Issue #6868

closed

Multi-repo-copy has an unintentional requirement for the repo pairs to be provided in a particular order

Added by dalley about 2 years ago. Updated about 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Expected Behavior:

The order in which the user specifies their source and destination repositories in the advanced copy API's config object does not matter.

Actual behavior:

The code loops through the pairs of source and destination repositories one by one as it loads them into the solver, decides what to copy, and then creates the new repository versions, which means that when the copy operation is performed for repo pairs early in the list, the solver doesn't know about repos later in the list.

Solution:

Load everything into the solver first, and only after everything has been loaded perform the depsolving + copies.

Actions #1

Updated by pulpbot about 2 years ago

  • Status changed from ASSIGNED to POST

Added by dalley about 2 years ago

Revision 2a72980c

Fix a multi-repo-copy bug

Results of the copy accidentally depend on the order in which the user specified the source-destination repository pairs in the config.

closes: #6868 https://pulp.plan.io/issues/6868

[nocoverage]

Actions #2

Updated by dalley about 2 years ago

  • Status changed from POST to MODIFIED
Actions #3

Updated by ttereshc about 2 years ago

  • Sprint/Milestone set to Pulp RPM 3.4.0
Actions #4

Updated by ttereshc about 2 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF