Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Perform Forge-style puppet syncs where content units already exist in Pulp #269

Closed
jeremycline opened this issue May 24, 2016 · 2 comments
Closed

Perform Forge-style puppet syncs where content units already exist in Pulp #269

jeremycline opened this issue May 24, 2016 · 2 comments
Labels
Issue Type: Test Case
Milestone
Chongrui - Summer...

Comments

@jeremycline
Copy link
Contributor

This is from https://pulp.plan.io/issues/1937

The problem boiled down to the importer recognizing the content was already in Pulp, but failing to associate it with the repository.

The test steps would be as follows:

  1. upload or sync a module to repo1
  2. perform a sync on repo2 against a forge-style repository (one with a modules.json file) that includes the module from 1.
  3. Assert the module from 1. is in the published repo2.

To do this in pulp-admin, it could be something as simple as:

  1. pulp-admin puppet repo create --repo-id=repo1 --feed=http://forge.puppetlabs.com --queries=torssh
  2. pulp-admin puppet repo sync run --repo-id=repo1
  3. pulp-admin puppet repo create --repo-id=repo2 --feed=http://forge.puppetlabs.com --queries=torssh
  4. pulp-admin puppet repo sync run --repo-id=repo2
@Ichimonji10
Copy link
Contributor

Thanks for the clear explanation and the steps for reproducing. This looks easy to implement as an automated test case...

danuzclaudes added a commit to danuzclaudes/pulp-smash that referenced this issue Jun 7, 2016
@danuzclaudes
Fix up issue #1937
3c39e0e 
This commit fixes the issue: pulp#269.

It creates two repositories with the same feed content. By synchronizing
both repos, check if the 2nd repo would have content; otherwise, the
sync will fail.

[1] https://pulp.plan.io/issues/1937
@danuzclaudes danuzclaudes mentioned this issue Jun 7, 2016
Merged
danuzclaudes added a commit to danuzclaudes/pulp-smash that referenced this issue Jun 7, 2016
@danuzclaudes
Fix up issue #1937
34f21f1 
This commit fixes the issue: pulp#269.

It creates two repositories with the same feed content. By synchronizing
both repos, check if the 2nd repo would have content; otherwise, the
sync will fail.

[1] https://pulp.plan.io/issues/1937
danuzclaudes added a commit to danuzclaudes/pulp-smash that referenced this issue Jun 8, 2016
@danuzclaudes
Fix up issue #1937
08d63df 
This commit fixes the issue: pulp#269.

It creates two repositories with the same feed content. By synchronizing
both repos, check if the 2nd repo would have content; otherwise, the
sync will fail.

[1] https://pulp.plan.io/issues/1937
danuzclaudes added a commit to danuzclaudes/pulp-smash that referenced this issue Jun 8, 2016
@danuzclaudes
Fix up issue #1937
4ed1881 
This commit fixes the issue: pulp#269.

It creates two repositories with the same feed content. By synchronizing
both repos, check if the 2nd repo would have content; otherwise, the
sync will fail.

[1] https://pulp.plan.io/issues/1937
danuzclaudes added a commit to danuzclaudes/pulp-smash that referenced this issue Jun 9, 2016
@danuzclaudes
Fix up issue #1937
ca6a35e 
This commit fixes the issue: pulp#269.

It creates two repositories with the same feed content. By synchronizing
both repos, check if the 2nd repo would have content; otherwise, the
sync will fail.

[1] https://pulp.plan.io/issues/1937
@Ichimonji10
Copy link
Contributor

Fixed by #293.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue Type: Test Case
Projects
None yet
Milestone
Chongrui - Summer Internship
Development

No branches or pull requests
2 participants
@Ichimonji10 @jeremycline