Project

Profile

Help

Send by e-mail

Issue #4718

Module integrity is not preserved at copy time

Added by paji@redhat.com 3 months ago. Updated 27 days ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
ttereshc
Category:
-
Sprint/Milestone:
Pulp - 2.19.1
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
2.19.1
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 53

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.

Checklist

Related issues

Related to RPM Support - Story #3982: As a user, I can get artifacts which belong to a specific module CLOSED - WONTFIX Actions
Related to RPM Support - Test #4819: Update modulemd copy tests, module artifacts are always copied now NEW Actions

Associated revisions

Revision 37d4ac9c View on GitHub
Added by ttereshc 2 months ago

Always copy module with its artifacts

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

Revision 7ce210c9 View on GitHub
Added by ttereshc 2 months ago

Always copy module with its artifacts

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

(cherry picked from commit 37d4ac9c77c37e10c451fc80ce4e21b0ecf55831)

History

#1 Updated by daviddavis 3 months ago

  • Version set to 2.19.0
  • Tags Pulp 2 added

#2 Updated by ttereshc 3 months ago

  • Tracker changed from Issue to Story
  • Subject changed from Need a module copy --with-modular-rpms options to As a user, I can copy modules and their artifacts without dependencies
  • % Done set to 0

#3 Updated by ttereshc 3 months ago

  • Related to Story #3982: As a user, I can get artifacts which belong to a specific module added

#4 Updated by ttereshc 3 months ago

  • Tracker changed from Story to Issue
  • Subject changed from As a user, I can copy modules and their artifacts without dependencies to Modules integrity is not preserved at copy time
  • Description updated (diff)
  • Severity set to 2. Medium
  • Triaged set to No

#5 Updated by ttereshc 3 months ago

  • Subject changed from Modules integrity is not preserved at copy time to Module integrity is not preserved at copy time

#6 Updated by ttereshc 3 months ago

  • Description updated (diff)

#7 Updated by ttereshc 3 months ago

  • Checklist item Always copy module artifacts when a module is copied added
  • Checklist item Write a test issue to update tests inthis area added
  • Checklist item Update examples in the docs for advanced copy added

#8 Updated by ipanova@redhat.com 3 months ago

  • Description updated (diff)

#9 Updated by ipanova@redhat.com 3 months ago

  • Checklist item changed from Write a test issue to update tests inthis area to Write a test issue to update tests in this area
  • Checklist item Add release notes added

#10 Updated by ipanova@redhat.com 3 months ago

This looks good to me.

#11 Updated by dkliban@redhat.com 3 months ago

  • Platform Release set to 2.19.1

#12 Updated by ipanova@redhat.com 3 months ago

  • Sprint set to Sprint 52

#13 Updated by ttereshc 3 months ago

  • Triaged changed from No to Yes

#14 Updated by dkliban@redhat.com 3 months ago

  • Sprint/Milestone set to 2.19.1

#15 Updated by ipanova@redhat.com 3 months ago

  • Groomed changed from No to Yes

#16 Updated by rchan 2 months ago

  • Sprint changed from Sprint 52 to Sprint 53

#17 Updated by ttereshc 2 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc

#18 Updated by ttereshc 2 months ago

  • Related to Test #4819: Update modulemd copy tests, module artifacts are always copied now added

#19 Updated by ttereshc 2 months ago

  • Checklist item Always copy module artifacts when a module is copied set to Done
  • Checklist item Write a test issue to update tests in this area set to Done

#20 Updated by ttereshc 2 months ago

  • Checklist item Update examples in the docs for advanced copy set to Done
  • Checklist item Add release notes set to Done

#21 Updated by ttereshc 2 months ago

  • Status changed from ASSIGNED to POST

#22 Updated by ttereshc 2 months ago

  • Status changed from POST to MODIFIED

#23 Updated by ttereshc 2 months ago

#24 Updated by dkliban@redhat.com about 2 months ago

  • Status changed from MODIFIED to ON_QA

#25 Updated by dkliban@redhat.com about 2 months ago

  • Status changed from ON_QA to CLOSED - CURRENTRELEASE

Please register to edit this issue

Send by e-mail

Also available in: Atom PDF