Issue #1937
closed
Syncing a puppet module with the same content as a different repo results in no content
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
Updated by mhrivnak over 8 years ago
Are you describing an upload, or a sync? Uploads usually don't use a "feed", but syncs do.
If you're describing a sync, I assume you're using a PULP_MANIFEST file in the directory?
Updated by jomitsch@redhat.com over 8 years ago
mhrivnak wrote:
Are you describing an upload, or a sync? Uploads usually don't use a "feed", but syncs do.
If you're describing a sync, I assume you're using a PULP_MANIFEST file in the directory?
Yes, 'upload' may have been misleading, I am describing creating two repos and syncing them
Updated by jcline@redhat.com over 8 years ago
- Status changed from NEW to POST
- Assignee set to jcline@redhat.com
Added by Jeremy Cline over 8 years ago
Updated by jcline@redhat.com over 8 years ago
Updated by jcline@redhat.com over 8 years ago
I've also filed https://github.com/PulpQE/pulp-smash/issues/269
Updated by Anonymous over 8 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp_puppet:577bd40946f14e3385c8d63f9ed29b26b64954b5.
Added by Jeremy Cline over 8 years ago
Revision 1cb6c874 | View on GitHub
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
Updated by jcline@redhat.com over 8 years ago
- Platform Release set to 2.8.5
The associated revisions looks weird because I accidentally merged this into master rather than 2.8-dev, so I cherry-picked it and merged-forward. The commit you should use to see if a branch/tag contains this fix is 1cb6c874e0c0c09200053126d853773b6708b62f
Updated by semyers over 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Updated by mhrivnak over 8 years ago
- Project changed from Pulp to Puppet Support
.
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