Project

Profile

Help

Story #1758

closed

As a user, I would like to be able to change timeout values

Added by jomitsch@redhat.com over 6 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
2.18.0
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 42
Quarter:

Description

An issue a Katello user [1] was having was able to be resolved by adjusting the values here [2] If this was available to be easily changed in a configuration, it would be beneficial to users.

[1] https://groups.google.com/forum/#!topic/foreman-users/J8xvzGHbz9w
[2] https://github.com/pulp/nectar/blob/python-nectar-1.3.3-1/nectar/config.py#L33

Since the nectar config already supports these as configurable options, it may be easy for a plugin to allow those values. It could be as simple has having validation recognize the setting, and documenting it.

Actions #2

Updated by mhrivnak almost 6 years ago

  • Description updated (diff)
Actions #3

Updated by taylorcw almost 5 years ago

+1 Would love to see this added.

Actions #4

Updated by ttereshc over 4 years ago

  • Priority changed from Normal to High
  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes
Actions #5

Updated by dkliban@redhat.com over 4 years ago

  • Sprint set to Sprint 41
Actions #6

Updated by daviddavis over 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to daviddavis
Actions #7

Updated by daviddavis over 4 years ago

  • Status changed from ASSIGNED to POST
Actions #8

Updated by rchan over 4 years ago

  • Sprint changed from Sprint 41 to Sprint 42
Actions #9

Updated by rchan about 4 years ago

Do we think this will make 2.18.0 and if so, should we mark it?
Or is this a 2.17.z stream item?

Actions #10

Updated by daviddavis about 4 years ago

  • Sprint/Milestone set to 2.18.0

rchan, I think 2.18.0 makes sense since it's new functionality. I've added it to the 2.18.0 milestone.

Added by daviddavis about 4 years ago

Revision 21e6886c

Exposing config options for read_timeout and connect_timeout

fixes #1758 https://pulp.plan.io/issues/1758

Actions #11

Updated by daviddavis about 4 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #12

Updated by dkliban@redhat.com about 4 years ago

  • Platform Release set to 2.18.0
Actions #13

Updated by ttereshc about 4 years ago

  • Status changed from MODIFIED to 5
Actions #14

Updated by ttereshc almost 4 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #15

Updated by bmbouter over 3 years ago

  • Tags Pulp 2 added
Actions #16

Updated by rchan over 3 years ago

Does Pulp 3 already offer this capability or do we need to create a related issue to ensure this feature is available in Pulp 3?

Actions #17

Updated by bmbouter over 3 years ago

We need to create a related issue. Currently we offer options like concurrency, but these would be good options also.

Also the current options can be seen here: https://docs.pulpproject.org/en/3.0/nightly/restapi.html#operation/remotes_file_file_create

Also available in: Atom PDF