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.

Bug 1334989

Summary: [RFE] Pulp download timeouts should be configurable
Product: Red Hat Satellite Reporter: Prakash Ghadge <pghadge>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.8CC: aeladawy, aganbat, ahumbe, andy.speagle, bbuckingham, bkearney, bmbouter, cdonnell, dchaudha, dgross, dkliban, ehelms, ggainey, gpayelka, ipanova, jalviso, jsherril, kkinge, ktordeur, ltran, mmccune, mpusater, ofalk, pcreech, peter.vreman, rajukuma, rbertolj, rchan, redhat-bugzilla, rjerrido, sadas, sjose8, smajumda, sokeeffe, ttereshc, vsedmik
Target Milestone: 6.10.0Keywords: FutureFeature, PrioBumpField, PrioBumpGSS, PrioBumpPM, Reopened, Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:08:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1971076    
Bug Blocks: 1122832    

Comment 2 Brad Buckingham 2016-11-21 17:12:25 UTC 
Created redmine issue http://projects.theforeman.org/issues/17423 from this bug
Comment 3 pulp-infra@redhat.com 2016-11-21 18:55:20 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2016-11-21 18:55:23 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2018-08-01 16:10:02 UTC 
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 9 pulp-infra@redhat.com 2018-08-07 20:06:52 UTC 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2018-08-10 19:08:48 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 11 pulp-infra@redhat.com 2018-09-04 18:06:33 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 13 pulp-infra@redhat.com 2018-11-20 19:36:46 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 14 pulp-infra@redhat.com 2018-12-04 22:35:52 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 18 Tanya Tereshchenko 2020-01-03 10:59:48 UTC 
Brad, it doesn't seem like there is anything to do on Pulp side. Should we move it to another component to track it there? Thanks!
Comment 19 Tanya Tereshchenko 2020-03-31 08:42:49 UTC 
This BZ is repurposed, this feature needs to be implemented in Pulp 3.

(FWIW, the feature is complete in Pulp 2 (released in 2.18.0), if anyone needs/wants to use it, see https://pulp.plan.io/issues/1758.)
Comment 20 pulp-infra@redhat.com 2020-03-31 17:48:25 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 21 pulp-infra@redhat.com 2020-03-31 17:48:27 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 24 pulp-infra@redhat.com 2020-05-08 19:31:05 UTC 
The Pulp upstream bug priority is at Low. Updating the external tracker on this bug.
Comment 26 Brad Buckingham 2020-07-06 21:42:45 UTC 
Hi Tanya,

Since we'll need this functionality in Pulp (v3) before it is added in to Katello, I am moving the bugzilla back to the Pulp component.  Once it is available in Pulp 3, we can move it back to Repositories component and complete the work needed in Katello.

Thanks!
Comment 27 pulp-infra@redhat.com 2020-10-26 17:07:07 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 28 pulp-infra@redhat.com 2020-10-26 17:07:08 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 29 pulp-infra@redhat.com 2020-11-02 21:04:08 UTC 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 30 pulp-infra@redhat.com 2020-11-13 23:04:49 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 31 pulp-infra@redhat.com 2020-12-03 21:05:23 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 32 pulp-infra@redhat.com 2020-12-07 20:06:03 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 37 Bryan Kearney 2021-04-13 10:12:30 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/17423 has been resolved.
Comment 38 Lai 2021-06-10 17:44:36 UTC 
Not sure how to test this as there's no test steps in the PR.  I'm only aware of syncing repos.
Comment 39 Justin Sherrill 2021-06-10 17:56:15 UTC 
You can change the setting at 

Administer > settings > Content > Sync Connection Timeout	

Changes take affect on next sync.


It defaults to 5 minutes, which should be plenty.  I don't have a great solution for testing it.  Maybe setting it to something really low (like 1 second), and trying to sync from a repo really far away?


You could also confirm in pulp's db:

sudo -u postgres psql pulpcore -c 'select url, total_timeout from core_remote;'
Comment 45 errata-xmlrpc 2021-11-16 14:08:26 UTC 
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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702