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.
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.
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.
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