Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1746589

Summary: Capsule-sync failing on Katello::Errors::PulpError: PLP0034 when you have puppet repo enaled and sync
Product: Red Hat Satellite Reporter: Ganesh Payelkar <gpayelka>
Component: Capsule - ContentAssignee: Partha Aji <paji>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: janarula, mmccune, vijsingh, vsedmik, zhunting
Target Milestone: 6.6.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-katello-3.12.0.24-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1759873 (view as bug list) Environment:
Last Closed: 2019-10-22 19:48:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1759873    

Description Ganesh Payelkar 2019-08-28 21:05:49 UTC 
Description of problem:

Capsule sync failing on Katello::Errors::PulpError: PLP0034 when you have  puppet repo

Version-Release number of selected component (if applicable):

satellite-6.6.0-6.el7sat.noarch
pulp-server-2.19.1.1-1.el7sat.noarch

How reproducible:

New installation of 6.6 Beta

Steps to Reproduce:
1. Sync/upload puppet a module with multiple versions.
2. Associate an environment to the capsule.
3. Start capsule sync task

Actual results:

# hammer capsule content synchronize --id="2"

[...............................................................] [100%]
Error: PLP0034: The distributor d38f24d0-9471-4590-99dd-e3ae20bffb85 indicated a failed response when publishing repository d38f24d0-9471-4590-99dd-e3ae20bffb85.




Expected results:


Additional info:


Aug 29 02:18:33 vm253-155 foreman: GET: https://satelllite/pulp/api/v2/tasks/185e9552-2c75-4770-a61f-ff9f730adde8/: {"content_type"=>"application/json", "accept"=>"application/json"}#012Res
ponse: 200: {"exception": null, "task_type": "pulp.server.managers.repo.publish.publish", "_href": "/pulp/api/v2/tasks/185e9552-2c75-4770-a61f-ff9f730adde8/", "task_id": "185e9552-2c75-4770-a61f-ff9f730adde8", "
tags": ["pulp:repository:d38f24d0-9471-4590-99dd-e3ae20bffb85", "pulp:action:publish"], "finish_time": "2019-08-28T20:48:30Z", "_ns": "task_status", "start_time": "2019-08-28T20:48:24Z", "traceback": "Traceback 
(most recent call last):\n  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 367, in trace_task\n    R = retval = fun(*args, **kwargs)\n  File \"/usr/lib/python2.7/site-packages/pulp/server/as
ync/tasks.py\", line 539, in __call__\n    return super(Task, self).__call__(*args, **kwargs)\n  File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 108, in __call__\n    return super(Pulp
Task, self).__call__(*args, **kwargs)\n  File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 622, in __protected_call__\n    return self.run(*args, **kwargs)\n  File \"/usr/lib/python2.7/site-pac
kages/pulp/server/controllers/repository.py\", line 1110, in publish\n    result = check_publish(repo_obj, dist_id, dist_inst, transfer_repo, conduit, call_config)\n  File \"/usr/lib/python2.7/site-packages/pulp
/server/controllers/repository.py\", line 1207, in check_publish\n    result = _do_publish(repo_obj, dist_id, dist_inst, transfer_repo, conduit, call_config)\n  File \"/usr/lib/python2.7/site-packages/pulp/serve
r/controllers/repository.py\", line 1265, in _do_publish\n    distributor_id=dist_id, summary=publish_report.summary\nPulpCodedException: The distributor d38f24d0-9471-4590-99dd-e3ae20bffb85 indicated a failed r
esponse when publishing repository d38f24d0-9471-4590-99dd-e3ae20bffb85.\n", "spawned_tasks": [], "progress_report": {}, "queue": "reserved_resource_worker-1", "state": "erro
r", "worker_name": "reserved_resource_worker-1.pnq2.redhat.com", "result": null, "error": {"code": "PLP0034", "data": {"distributor_id": "d38f24d0-9471-4590-99dd-e3ae20bffb85", "repo_id": "d38f2
4d0-9471-4590-99dd-e3ae20bffb85", "summary": "duplicate unit names"}, "description": "The distributor d38f24d0-9471-4590-99dd-e3ae20bffb85 indicated a failed response when publishing repository d38f24d0-9471-459
0-99dd-e3ae20bffb85.", "sub_errors": []}, "_id": {"$oid": "5d66e8989ec5ac061be93d77"}, "id": "5d66e8989ec5ac061be93d77"}



On capsule : 

Aug 29 02:18:30  pulp: pulp.server.controllers.repository:INFO: [185e9552] duplicate unit names
Aug 29 02:18:30 pulp: pulp.server.controllers.repository:ERROR: [185e9552] (3881-58464) Exception caught from plugin during publish for repo [d38f24d0-9471-4590-99dd-e3ae20bffb85]
Aug 29 02:18:30  pulp: pulp.server.controllers.repository:ERROR: [185e9552] (3881-58464) Traceback (most recent call last):
Aug 29 02:18:30  pulp: pulp.server.controllers.repository:ERROR: [185e9552] (3881-58464)   File "/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py", line 1265, in _do_publish
Aug 29 02:18:30  pulp: pulp.server.controllers.repository:ERROR: [185e9552] (3881-58464)     distributor_id=dist_id, summary=publish_report.summary
Aug 29 02:18:30  pulp: pulp.server.controllers.repository:ERROR: [185e9552] (3881-58464) PulpCodedException: The distributor d38f24d0-9471-4590-99dd-e3ae20bffb85 indicated a failed response when publishing repository d38f24d0-9471-4590-99dd-e3ae20bffb85.
Aug 29 02:18:30  pulp: pulp.server.async.tasks:INFO: [185e9552] Task failed : [185e9552-2c75-4770-a61f-ff9f730adde8] : The distributor d38f24d0-9471-4590-99dd-e3ae20bffb85 indicated a failed response when publishing repository d38f24d0-9471-4590-99dd-e3ae20bffb85.
Aug 29 02:18:30  pulp: celery.app.trace:INFO: [185e9552] Task pulp.server.managers.repo.publish.publish[185e9552-2c75-4770-a61f-ff9f730adde8] raised expected: PulpCodedException()
Comment 4 Partha Aji 2019-09-10 21:01:36 UTC 
Connecting redmine issue https://projects.theforeman.org/issues/27825 from this bug
Comment 5 Bryan Kearney 2019-09-11 22:04:08 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27825 has been resolved.
Comment 8 Lukas Pramuk 2019-09-20 12:28:00 UTC 
VERIFIED.

@Satellite 6.6.0 Snap 20.1
tfm-rubygem-katello-3.12.0.25-1.el7sat.noarch

by the manual reproducer described in comment#0:

1. Sync puppet repo containing puppetlabs-stdlib module with multiple versions:
- puppetlabs-stdlib-4.21.0
- puppetlabs-stdlib-4.22.0
- puppetlabs-stdlib-4.23.0

2. Associate Library environment to the capsule

3. Start capsule sync task

# hammer capsule content synchronize --id="2"
[....................................................................................] [100%]

>>> capsule sync succeeded
Comment 11 Brad Buckingham 2019-10-11 11:44:06 UTC 
*** Bug 1759873 has been marked as a duplicate of this bug. ***
Comment 12 Bryan Kearney 2019-10-22 19:48:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3172