Project

General

Profile

Bug #13580

PLP0034: The distributor indicated a failed response when publishing repository

Added by Fil Di Noto about 3 years ago. Updated 10 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

I'm getting this error when I try to publish new content view versions.

PLP0034: The distributor indicated a failed response when publishing repository

When I open the task in Dynflow and skip the step " Actions::Pulp::Repository::DistributorPublish (error) [ 849.95s / 0.31s ] " the task completes and it seems as if the version published correctly. This seems to have started happening around the same time that I started making puppet repos.

History

#1 Updated by Fil Di Noto about 3 years ago

I think my workaround has a side effect of not making the modules visible in other parts of the UI. I can't see/select any of the modules when editing a host.

#2 Updated by Fil Di Noto about 3 years ago

---
pulp_tasks:
- exception:
task_type: pulp.server.managers.repo.publish.publish
href: /pulp/api/v2/tasks/a89dc14a-e133-4d53-bd29-34ce535078c3/
task_id: a89dc14a-e133-4d53-bd29-34ce535078c3
tags:
- pulp:repository:ORG-Library-g222-el7-basic
- pulp:action:publish
finish_time: '2016-02-05T18:04:51Z'
_ns: task_status
start_time: '2016-02-05T18:04:51Z'
traceback: ! "Traceback (most recent call last):\n File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\",
line 240, in trace_task\n R = retval = fun(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\",
line 328, in call\n return super(Task, self).
_call__(*args, **kwargs)\n
\ File \"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 437, in
protected_call\n return self.run(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/pulp/server/managers/repo/publish.py\",
line 99, in publish\n transfer_repo, conduit, call_config)\n File \"/usr/lib/python2.7/site-packages/pulp/server/managers/repo/publish.py\",
line 131, in _do_publish\n repository_id=repo_id, distributor_id=distributor_id)\nPulpCodedException:
The distributor ORG-Library-g222-el7-basic indicated a failed response when
publishing repository ORG-Library-g222-el7-basic.\n"
spawned_tasks: []
progress_report: {}
queue:
state: error
worker_name:
result:
error:
code: PLP0034
data:
repository_id: ORG-Library-g222-el7-basic
distributor_id: ORG-Library-g222-el7-basic
description: The distributor ORG-Library-g222-el7-basic indicated a failed response
when publishing repository ORG-Library-g222-el7-basic.
sub_errors: []
_id:
$oid: 56b4e4435c3bc862697d4011
id: 56b4e4438595b24c7382373a
poll_attempts:
total: 2
failed: 0

#3 Updated by Fil Di Noto about 3 years ago

I stopped getting this error after I removed all content views and composite content views that contained puppet modules.

Fil Di Noto wrote:

I'm getting this error when I try to publish new content view versions.

PLP0034: The distributor indicated a failed response when publishing repository

When I open the task in Dynflow and skip the step " Actions::Pulp::Repository::DistributorPublish (error) [ 849.95s / 0.31s ] " the task completes and it seems as if the version published correctly. This seems to have started happening around the same time that I started making puppet repos.

#4 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 113 to 86

Check that /etc/puppet/environments is writeable by apache.

#5 Updated by Eric Helms about 3 years ago

  • Status changed from New to Need more information

#6 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 144

#7 Updated by Eric Helms almost 3 years ago

  • Legacy Backlogs Release (now unused) changed from 144 to 168

#8 Updated by Eric Helms almost 3 years ago

  • Legacy Backlogs Release (now unused) changed from 168 to 171

#9 Updated by Eric Helms almost 3 years ago

  • Legacy Backlogs Release (now unused) deleted (171)

#10 Updated by Justin Sherrill almost 3 years ago

  • Status changed from Need more information to Rejected
  • Legacy Backlogs Release (now unused) set to 166

please reopen if you are still seeing this issue. Thanks

Also available in: Atom PDF