-
Notifications
You must be signed in to change notification settings - Fork 44
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.
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
Perform Forge-style puppet syncs where content units already exist in Pulp #269
Labels
Milestone
Comments
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
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
Merged
danuzclaudes
added a commit
to danuzclaudes/pulp-smash
that referenced
this issue
Jun 7, 2016
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
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
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
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
Fixed by #293. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
To do this in pulp-admin, it could be something as simple as:
The text was updated successfully, but these errors were encountered: