From closed bug here we have a user hitting a timeout during manifest import: https://bugzilla.redhat.com/show_bug.cgi?id=1334627#c2 """ I also encountered that on my testinstall, however my pulp was running fine while the initial import of the Manifest errored out with "RestClient::RequestTimeout: Katello::Resources::Candlepin::Owner: Request Timeout (POST /candlepin/owners/ACME/imports)" For me just clicking "refresh manifest" was enough to fix that issue, though. """ It looks like for 6.2 we regressed back to the old 120 second timeout: :katello: :rest_client_timeout: 120 where in 6.1 we had this set to :rest_client_timeout: 3600 we need to move this back to 3600 until we resolve ALL issues with async operations.
See this Candlepin RFE that is not complete: https://bugzilla.redhat.com/show_bug.cgi?id=1313551
*** Bug 1329091 has been marked as a duplicate of this bug. ***
Upstream bug component is Content Management
Is there a working workaround? I have increased the limit: sed 's/:rest_client_timeout:.*/:rest_client_timeout: 5000/' -i /etc/foreman/plugins/katello.yaml Restarted all the services. But I am still getting a timeout after cca 120 seconds. It looks like the value is not being honored.
So after few more tries, it started working. But I restarted all services for sure, not following...
*** Bug 1334383 has been marked as a duplicate of this bug. ***
Verified in Satellite 6.2 Beta Snap 14. After 10 manifest imports, with various subscription combinations, I have not encountered the timeout issues seen in previous snaps. additionally [root@rhsm-qe-1 ~]# cat /etc/foreman/plugins/katello.yaml | grep timeout :rest_client_timeout: 3600
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/RHBA-2016:1501