Project

Profile

Help

Issue #4693

closed

Module Streams not copying correctly with recursive and recursive_conservative

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

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.19.0
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

  1. Create and sync the following yum repo (Source) -> https://partha.fedorapeople.org/test-repos/pteradactyl/

  2. Create another repo Dest which will serve as the destination repo

  3. Go to mongo and pick up a uuid for the pteradactly:2 module stream. This stream will be copied from source to dest .

  4. run the following command

    https://<fqdn>/pulp/api/v2/repositories/Dest/actions/associate/: {"source_repo_id":"Source","criteria":{"type_ids":["modulemd"],"filters":{"association":{"unit_id":{"$in":[<$MODULE UUID>]}}}},"override_config":{"recursive":true}}: {"content_type"=>"application/json", "accept"=>"application/json"}
    
  5. pulp-admin rpm repo list. Check for the number of module mds copied over by the above call.

  6. notice that with recursive set to true all the pteradactyl module streams gets copied over, instead of just pteradactly:2 and packages belonging to that

  7. Behavior is similar for recursive conservative


Related issues

Related to RPM Support - Issue #4962: Modules are incorrectly copied when their artifacts shadow the names of non-modular RPM dependenciesCLOSED - WONTFIXActions
Copied to RPM Support - Test #5320: Module Streams not copying correctly with recursive and recursive_conservative CLOSED - WONTFIXActions

Also available in: Atom PDF