Project

Profile

Help

Issue #4718

closed

Module integrity is not preserved at copy time

Added by paji@redhat.com almost 5 years ago. Updated over 4 years ago.

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

Description

In Pulp 2.19 copying modules does not automatically copy over rpms.

Using recursive:True tries to dep solve and copies not only rpms but dependent module streams and their dependent rpms (could be a a fairly expensive operation.)

To preserve module integrity and help users not to break module content easily, all available artifacts should always be copied (without their dependencies). No error is raised if any artifacts are unavailable in a source/destination repo.
To include dependencies, one still should use --recursive or --recursive-conservative flag.


Related issues

Related to RPM Support - Story #3982: As a user, I can get artifacts which belong to a specific moduleCLOSED - WONTFIX

Actions
Related to RPM Support - Test #4819: Update modulemd copy tests, module artifacts are always copied nowCLOSED - DUPLICATEActions

Also available in: Atom PDF