Project

Profile

Help

Issue #1895

closed

Recursive RPM unit copies are not recursive

Added by Ichimonji10 almost 8 years ago. Updated about 5 years ago.

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

Description

It's possible to create an RPM repository, sync content into it, create a second RPM repository, and recursively copy a unit from the first repository to the second. The steps go something like this:

pulp-admin rpm repo create --repo-id source --feed https://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/zoo/
pulp-admin rpm repo sync run --repo-id sorce
pulp-admin rpm repo create --repo-id target
pulp-admin rpm repo copy rpm --from-repo-id source --to-repo-id target --str-eq="name=chimpanzee" --recursive
pulp-admin rpm repo content rpm --repo-id target | grep 'Name:'

If a regular copy was done, then only the "chimpanzee" unit should be copied over. But since a recursive copy was done, both the chimpanzee unit and all of its dependencies should be copied over. This isn't happening. As things stand, the --recursive flag appears to have no effect, and only the "chimpanzee" unit is copied.

The log files contain no tracebacks. journalctl --full shows only entries like this when a unit is copied from the source repo to the target repo:

May 04 16:52:59 cloud-qe-3.idmqe.lab.eng.bos.redhat.com pulp[1000]: celery.worker.job:INFO: Task pulp.server.managers.repo.unit_association.associate_from_repo[751f08f0-bc56-41b8-950e-834b744cf52c] succeeded in 0.0327394460328s: {'units_successful': [{'unit_key': {'name': u'chimpanzee', 'checksum':...

Tested with Pulp 2.8.3 on Fedora 22 and 23.

Also available in: Atom PDF