Actions
Issue #1937
closed
Syncing a puppet module with the same content as a different repo results in no content
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.8.3
Platform Release:
2.8.5
OS:
CentOS 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Found this when doing capsule syncs in Katello (pulp to pulp sync) but also was able to reproduce on a single pulp server.
The issue:
A puppet module is uploaded to puppet repo A and then when the same puppet module is uploaded to puppet module B (both using the same feed), puppet module B has no content.
puppet repo B, there is no content
/var/lib/pulp/published/puppet/https/repos/Default_Organization-prod1-pup1
To reproduce:
attached is a puppet module tarball to make it easier to reproduce
1) Create a puppet repo with the feed pointed at the tarball, notice that the relevant content shows in the repo's filepath
2) Create a puppet repo with the same feed, notice that the relevant content does not show in this repos filepath
Files
Actions
.
Forge importer now queries the repo units instead of all units
This commit fixes a problem where the Forge importer would skip importing units into a repository if the unit already existed in Pulp. This patch does not address the problem that the importer will download a module even if it already exists within Pulp; that issue is being tracked in https://pulp.plan.io/issues/1943
fixes #1937