Actions
Issue #1440
closedPuppet repository doesn't sync second and consequent repositories
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
2.8.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Steps to reproduce bug:
-
Create puppet repository
repo1
with feed containing pulp manifest (auto_publish=True) -
Sync
repo1
-
Create puppet repository
repo2
with feed containing pulp manifest (auto_publish=True) -
Sync
repo2
repo1
now contains 2 units as expected, whilerepo2
is empty. This happens only on development version of pulp, not in 2.7 or 2.6.$ pulp-admin puppet repo create --repo-id=repo1 --feed=https://repos.fedorapeople.org/pulp/pulp/demo_repos/puppet_manifest/modules/ Successfully created repository [repo1] [root@ec2-54-216-139-81 ~]# pulp-admin puppet repo sync run --repo-id repo1 +----------------------------------------------------------------------+ Synchronizing Repository [repo1] +----------------------------------------------------------------------+ This command may be exited via ctrl+c without affecting the request. Downloading metadata... [==================================================] 100% Metadata Query: 1/1 items ... completed Downloading new modules... [==================================================] 100% Module: 2/2 items ... completed Task Succeeded Publishing modules... [==================================================] 100% Module: 2/2 items ... completed Generating repository metadata... [-] ... completed Publishing repository over HTTP... ... completed Publishing repository over HTTPS... ... skipped Task Succeeded $ pulp-admin puppet repo list +----------------------------------------------------------------------+ Puppet Repositories +----------------------------------------------------------------------+ Id: repo1 Display Name: None Description: None Content Unit Counts: Puppet Module: 2 $ pulp-admin puppet repo create --repo-id=repo2 --feed=https://repos.fedorapeople.org/pulp/p ulp/demo_repos/puppet_manifest/modules/ Successfully created repository [repo2] $ pulp-admin puppet repo sync run --repo-id repo2 +----------------------------------------------------------------------+ Synchronizing Repository [repo2] +----------------------------------------------------------------------+ This command may be exited via ctrl+c without affecting the request. Downloading metadata... [==================================================] 100% Metadata Query: 1/1 items ... completed Downloading new modules... [==================================================] 100% Module: 0/0 items ... completed Task Succeeded Publishing modules... [==================================================] 100% Module: 0/0 items ... completed Generating repository metadata... [-] ... completed Publishing repository over HTTP... ... completed Publishing repository over HTTPS... ... skipped Task Succeeded $ pulp-admin puppet repo list +----------------------------------------------------------------------+ Puppet Repositories +----------------------------------------------------------------------+ Id: repo1 Display Name: None Description: None Content Unit Counts: Puppet Module: 2 Id: repo2 Display Name: None Description: None Content Unit Counts: $
Updated by mhrivnak almost 9 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
- Priority changed from Normal to High
- Platform Release set to 2.8.0
- Triaged changed from No to Yes
Updated by dkliban@redhat.com almost 9 years ago
I was able to reproduce this on 2.8.0 nightly build.
Updated by dkliban@redhat.com almost 9 years ago
Just tested on 2.7.1 and did not see the same behavior. This is definitely a regression.
This seems to only occur when the modules in the second repository have previously been imported into Pulp (via a different repo).
Updated by rbarlow almost 9 years ago
- Project changed from Pulp to Puppet Support
- Category deleted (
14)
Updated by dkliban@redhat.com almost 9 years ago
- Status changed from ASSIGNED to POST
Added by dkliban@redhat.com almost 9 years ago
Updated by dkliban@redhat.com almost 9 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 91bc0c584c45e75d4dc98f994588025afcf0eb62.
Updated by dkliban@redhat.com over 8 years ago
- Status changed from MODIFIED to 5
Updated by dkliban@redhat.com over 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Adds use of GetLocalUnitsStep to track which units already exist in Pulp
During conversion to mongoengine the check for already existing units broke. This fixes that problem.
https://pulp.plan.io/issues/1440 closes #1440