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 2181249

Summary: Repository sync tasks hanging with message 'Request timed out' instead of failing with error.
Product: Red Hat Satellite Reporter: Krutika Kinge <kkinge>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.5CC: ahumbe, dalley, peter.vreman
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:11:29 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:

Description Krutika Kinge 2023-03-23 12:43:20 UTC 
Description of problem:
Repository sync tasks hanging with below error message:
~~~~
Mar 16 12:14:03 satellite.example.com pulpcore-worker-5[1963733]: Backing off download_wrapper(...) for 0.5s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/repodata/0ca1810e4506790be5b8ab5c3f871dd9df8443a32b502c25990b9a7033a482c4-filelists.xml.gz. Increasing the total_timeout value on the remote might help.)
Mar 16 12:14:03 satellite.example.com pulpcore-worker-5[1963733]: pulp [112f5f93-b368-4c4b-b9a8-7e5129539a10]: backoff:INFO: Backing off download_wrapper(...) for 0.5s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/repodata/0ca1810e4506790be5b8ab5c3f871dd9df8443a32b502c25990b9a7033a482c4-filelists.xml.gz. Increasing the total_timeout value on the remote might help.)
~~~~

The task should either finish or get failed with an error instead of waiting for a long time in hung state.

Version-Release number of selected component (if applicable):
6.11.5 and later

How reproducible:
In customer environment.

Steps to Reproduce:
NA

Actual results:
The task is in hung state for a long time instead of failing.

Expected results:
Task should fail with some error message.

Additional info:
Comment 1 Daniel Alley 2023-03-23 14:13:52 UTC 
From the description alone it's not clear that this is an issue, the "back off" means that it will wait a bit and try again later - after 3 *(by default) unsuccessful attempts it will fail as requested.

What are you seeing in practice?  Would you describe the problem as being that the backoff period is too long, is the timeout too low, retrying too many times before failure, or that it is not behaving as I've described above?
Comment 2 Peter Vreman 2023-03-23 15:33:27 UTC 
Below the log that it does a backoff of ~2 secs and 3 retries and then after one hour again. And after 5 hours i cancelled the job

~~~
Mar 16 04:04:25 li-lc-2751 pulpcore-worker-8[3683002]: pulp [9a7daf7a-4017-4c0b-b192-c8bfb59f9aac]: pulpcore.tasking.pulpcore_worker:INFO: Task completed 81a0216f-76b3-4512-840a-9297eed6110f
Mar 16 04:08:34 li-lc-2751 pulpcore-worker-2[3648617]: Backing off download_wrapper(...) for 0.9s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-7.0-source-built-artifacts-7.0.104-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 04:08:34 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: backoff:INFO: Backing off download_wrapper(...) for 0.9s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-7.0-source-built-artifacts-7.0.104-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 04:08:34 li-lc-2751 pulpcore-worker-2[3648617]: Backing off download_wrapper(...) for 0.6s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 04:08:34 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: backoff:INFO: Backing off download_wrapper(...) for 0.6s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 04:08:41 li-lc-2751 pulpcore-worker-7[3648565]: Backing off download_wrapper(...) for 0.0s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 04:08:41 li-lc-2751 pulpcore-worker-7[3648565]: pulp [90422827-a859-414f-aad2-62fbdbd807ea]: backoff:INFO: Backing off download_wrapper(...) for 0.0s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 05:08:34 li-lc-2751 pulpcore-worker-2[3648617]: Backing off download_wrapper(...) for 1.7s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 05:08:34 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: backoff:INFO: Backing off download_wrapper(...) for 1.7s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 05:08:42 li-lc-2751 pulpcore-worker-7[3648565]: Backing off download_wrapper(...) for 1.1s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 05:08:42 li-lc-2751 pulpcore-worker-7[3648565]: pulp [90422827-a859-414f-aad2-62fbdbd807ea]: backoff:INFO: Backing off download_wrapper(...) for 1.1s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 06:08:37 li-lc-2751 pulpcore-worker-2[3648617]: Backing off download_wrapper(...) for 2.2s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 06:08:37 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: backoff:INFO: Backing off download_wrapper(...) for 2.2s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 06:08:44 li-lc-2751 pulpcore-worker-7[3648565]: Backing off download_wrapper(...) for 3.6s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 06:08:44 li-lc-2751 pulpcore-worker-7[3648565]: pulp [90422827-a859-414f-aad2-62fbdbd807ea]: backoff:INFO: Backing off download_wrapper(...) for 3.6s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 07:08:40 li-lc-2751 pulpcore-worker-2[3648617]: Backing off download_wrapper(...) for 4.8s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 07:08:40 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: backoff:INFO: Backing off download_wrapper(...) for 4.8s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 07:08:48 li-lc-2751 pulpcore-worker-7[3648565]: Backing off download_wrapper(...) for 1.3s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 07:08:48 li-lc-2751 pulpcore-worker-7[3648565]: pulp [90422827-a859-414f-aad2-62fbdbd807ea]: backoff:INFO: Backing off download_wrapper(...) for 1.3s (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]: Giving up download_wrapper(...) after 5 tries (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: backoff:ERROR: Giving up download_wrapper(...) after 5 tries (pulpcore.exceptions.base.TimeoutException: Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: pulpcore.tasking.pulpcore_worker:INFO: Task af406681-dfaa-427b-8616-22748199bb54 failed (Request timed out for https://cdn.redhat.com/content/dist/rhel8/8.7/x86_64/codeready-builder/os/Packages/d/dotnet-sdk-6.0-source-built-artifacts-6.0.115-1.el8_7.x86_64.rpm. Increasing the total_timeout value on the remote might help.)
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]: pulp [dd1bfa18-caf8-45a2-8d38-c7ba10900550]: pulpcore.tasking.pulpcore_worker:INFO:   File "/usr/lib/python3.9/site-packages/pulpcore/tasking/pulpcore_worker.py", line 410, in _perform_task
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]:    result = func(*args, **kwargs)
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]:  File "/usr/lib/python3.9/site-packages/pulp_rpm/app/tasks/synchronizing.py", line 568, in synchronize
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]:    repo_version = dv.create() or repo.latest_version()
Mar 16 08:08:45 li-lc-2751 pulpcore-worker-2[3648617]:  File "/usr/lib/python3.9/site-packages/pulpcore/plugin/stages/declarative_version.py", line 161, in create

~~~
Comment 3 Daniel Alley 2023-03-23 15:55:18 UTC 
Thanks, that's helpful.  It seems like the issue may be that the repo in question contains a large number of huge multi-gigabyte packages, resulting in saturation of the connection, and individual downloads start timing out.

Have you configured any of the timeout settings or are they set to the defaults?
Comment 5 Eric Helms 2024-06-06 16:11:29 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.