Random 502 error when publishing new content

Support
,
1

Hi all,

I think I’ve seen this happening already in some old posts, but I am not sure how to handle this one, and I don t want to revive old threads.

Problem:
When publishing new content after adding repos, at 40% of sync, the task pauses with the error:"

Error message: the server returns an error
HTTP status code: 502
Response headers: {“date”=>“Mon, 31 May 2021 14:19:33 GMT”, “server”=>“Apache”, “content-length”=>“445”, “connection”=>“close”, “content-type”=>“text/html; charset=iso-8859-1”}
Response body:

502 Proxy Error

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /pulp/api/v3/content/rpm/packages/.

Reason: Error reading from remote server

Expected outcome:

A clean task acoomplished

Foreman and Proxy versions:
2.3 Foreman Proxy

Foreman and Proxy plugin versions:
Katello 3.18.2.1

Distribution and version:
RHEL 8

Other relevant data:
If I force resume eventually the task ends with a 100% completion and no errors

Thanks for the support, I don t feel very confortable resuming paused error taks, although it completes. Should I ignore it, is it safe right now or should I try to re-publish it?

Thanks and cheers

Miguel de Amorim

2

I think this thread may help you: Issues Syncing Redhat yum repositories - #15 by Justin_Sherrill?

Keep in mind that this will be wiped out by an installer run.

in 4.0, some timeouts were increased which may help with a larger bulk size
in 4.1, this setting has been moved to a setting under Admister > Settings which survives installers runs

3

I also had problems syncing redhat repos, and managed to get repos through the initial sync by lowering concurrency.

But I still intermittently see this error when i publish or promote a content view, cant remember which, sorry.

The thing is…this happens during publish or promote. Not sync.

Why on earth should we be getting errors connecting to proxy, when all we are doing is publish or promote? Proxy should not have anything to do with publish or promote.

All i want to do is publish/promote the content i already have. I have not asked to sync… Publish/promote should not be going anywhere near the proxy…

4

Just happened again, on publish. Resume gets past the error, but its still pretty ridiculous, to have some error from proxy, when just publishing a repo.

1 Like