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 1787335 - Error: PLP0034: The distributor indicated a failed response when publishing repository.
Summary: Error: PLP0034: The distributor indicated a failed response when publishing r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.9.0
Assignee: Ian Ballou
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-02 12:48 UTC by Akshay Kapse
Modified: 2024-06-13 22:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:12:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
attaching the foreman-tail log (126.75 KB, text/plain)
2020-01-22 09:36 UTC, Akshay Kapse 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31115 0 Normal Closed Error: PLP0034: The distributor indicated a failed response when publishing repository. 2021-02-11 06:45:06 UTC
Red Hat Knowledge Base (Solution) 4852741 0 None None None 2020-02-24 13:37:45 UTC

Description Akshay Kapse 2020-01-02 12:48:24 UTC 
Description of problem:
# hammer content-view version promote --organization-id 1 --content-view-id 5 --to-lifecycle-environment "test" --id 32
[...............................................                                                                                                       ] [31%]
Error: PLP0034: The distributor XXXXXXX indicated a failed response when publishing repository XXXXXXXXXXXXX


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


How reproducible:
Easily

Steps to Reproduce:
1. Create a puppet repository and upload a puppet module.
2. Change the module version and build the puppet module again.
3. Upload the new puppet module into the repository:
hammer repository upload-content --organization "Default Organization" --product "<product_name>" --name "<repo_name>" --path <puppet_module_path>
4. Try to publish the content view:
# hammer content-view version promote --organization-id 1 --content-view-id 5 --to-lifecycle-environment "test" --id 32



Actual results:
Promoting content view fails with error:
Error: PLP0034: The distributor XXXXXXX indicated a failed response when publishing repository XXXXXXXXXXXXX


Expected results:
Should be able to publish the content view.
Comment 3 Brad Buckingham 2020-01-07 18:18:17 UTC 
Can you attach a foreman-debug, output from the production.log (with the full stack trace) or a task export that captures the error?
Comment 4 Justin Sherrill 2020-01-16 03:22:29 UTC 
in this case /var/log/messages with the traceback and that error would be very helpful
Comment 6 Akshay Kapse 2020-01-22 09:36:49 UTC 
Created attachment 1654499 [details]
attaching the foreman-tail log
Comment 8 Justin Sherrill 2020-09-01 13:16:31 UTC 
looking at the prior logs, the error was:

INFO: [7f63b091] duplicate unit names
ERROR: [7f63b091] (2828-38368) Exception caught from plugin during publish for repo [1-puppetcv-Library-puppet-d3e91605-6a38-47e0-8c99-986516673f7f]
ERROR: [7f63b091] (2828-38368) Traceback (most recent call last):
ERROR: [7f63b091] (2828-38368)   File "/usr/lib/python2.7/site-packages/pulp/server/controllers/repository.py", line 1265, in _do_publish
ERROR: [7f63b091] (2828-38368)     distributor_id=dist_id, summary=publish_report.summary
ERROR: [7f63b091] (2828-38368) PulpCodedException: The distributor 1-puppetcv-Library-puppet-d3e91605-6a38-47e0-8c99-986516673f7f indicated a failed response when publishing repository 1



It seems like incremental update is not removing an older version of the puppet module.
Comment 11 Ian Ballou 2020-10-20 17:17:34 UTC 
Created redmine issue https://projects.theforeman.org/issues/31115 from this bug
Comment 12 Bryan Kearney 2020-10-27 16:06:11 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31115 has been resolved.
Comment 13 Brad Buckingham 2020-11-13 19:00:45 UTC 
Fix is in Satellite 6.9 SNAP 1 with tfm-rubygem-katello-3.18.0-0.1.rc1.el7sat.noarch
Comment 14 Lai 2021-01-05 19:19:37 UTC 
Steps to test:

1. Get a hold of multiple versions of 2 or 3 different puppet modules
2. Upload the puppet modules to a repository
3. Create a content view with all of the older puppet modules and publish
4. Incrementally update the version you just created with the newest puppet modules with the following command: hammer content-view version incremental-update --puppet-module-ids <id> --content-view-version-id <id>
5. Check UI to see that the older puppet modules are removed
6. Promote the incremental content view version with the following command: hammer content-view version promote --organization-id <id> --content-view-id <id> --to-lifecycle-environment "<name of lce>" --id <id>

Expected result:
# hammer content-view version promote --organization-id 1 --content-view-id 4 --to-lifecycle-environment "Library" --id 7
[..............................................................................................................] [100%]

Successfuly promote to LCE

Actual Result:
# hammer content-view version promote --organization-id 1 --content-view-id 4 --to-lifecycle-environment "Library" --id 7
[..............................................................................................................] [100%]

Successfully promote to LCE

Verified on 6.9.0_07
Comment 17 errata-xmlrpc 2021-04-21 13:12:25 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 (Moderate: Satellite 6.9 Release), 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-2021:1313
Note You need to log in before you can comment on or make changes to this bug.