Project

General

Profile

Bug #15170

REST Timeout during manifest import

Added by Mike McCune over 3 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

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

Associated revisions

Revision 022e3d86 (diff)
Added by Mike McCune over 3 years ago

Fixes #15170 - Moving timeout to a large enough value

This is necessary because we have various operations in Katello that
are synchronus, especially around our interaction with candlepin and
manifest import that we will often time-out during operation.

We need to keep this timeout value high until the API calls we rely on
are implemented in an async manner.

Revision 4127ec11
Added by Mike McCune over 3 years ago

Merge pull request #129 from mccun934/20160524-1602

Fixes #15170 - Moving timeout to a large enough value

History

#1 Updated by Mike McCune over 3 years ago

  • Pull request https://github.com/Katello/puppet-katello/pull/129 added

#2 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) set to 143

#3 Updated by Mike McCune over 3 years ago

  • Status changed from New to Ready For Testing

#4 Updated by Anonymous over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF