Bug 2043144

Summary: After upgrading to 6.10, Satellite fails to sync some repositories with large files with timeout error
Product: Red Hat Satellite Reporter: Ashish Humbe <ahumbe>
Component: RepositoriesAssignee: Ian Ballou <iballou>
Status: CLOSED ERRATA QA Contact: Devendra Singh <desingh>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.1CC: avnkumar, desingh, dhjoshi, iballou, jsherril, mmccune, pcreech, saydas
Target Milestone: 6.11.0Keywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-4.3.0.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2043149 2053726 (view as bug list) Environment:
Last Closed: 2022-07-05 14:32:15 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:    
Bug Blocks: 2043149    
Attachments:
Description Flags
Reposync fails with timeout error none

Description Ashish Humbe 2022-01-20 17:23:04 UTC 
Created attachment 1852249 [details]
Reposync fails with timeout error

Description of problem:
After upgrading to 6.10, Satellite fails to sync some repositories with large files and displays the following error:

Request timed out for https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/4ae4b0b9f3e8e0ed6007d17625c04e36a3b01ec9-other.xml.gz. Increasing the total_timeout value on the remote might help. (Katello::Errors::Pulp3Error)

Increasing the default sync connection timeout from 300 to 3600 seconds helps in getting repos synced successfully. 

Web UI -> Administer -> Settings -> Content tab -> Sync Connection Timeout -> Set 3600

Steps to Reproduce:
1. After Sat6.9 -> 6.10 upgrade sync some RHEL base repos
2.
3.

Actual results:
Sync fails with the above error due to a smaller timeout value.

Expected results:
The default timeout value should be increased so sync will work successfully.

Additional info:
Comment 1 Justin Sherrill 2022-01-27 18:36:47 UTC 
*** Bug 2040788 has been marked as a duplicate of this bug. ***
Comment 2 Ian Ballou 2022-02-09 15:21:22 UTC 
Created redmine issue https://projects.theforeman.org/issues/34426 from this bug
Comment 8 Ian Ballou 2022-03-03 19:13:59 UTC 
*** Bug 2057660 has been marked as a duplicate of this bug. ***
Comment 9 Devendra Singh 2022-05-02 13:12:14 UTC 
Verified on 6.11 Snap18.5

Verification steps:

- Setup the Satellite of 6.10.z.
- Enable the large repositories
- Ran the sync and the sync job worked well.
- Perform the upgrade from 6.10.z to 6.11 Snap18.5 and it was completed successfully.
- Checked the updated changes for "Sync Connect Timeout" in the UI and it is updated to 60 seconds.

  UI -> Administer -> Settings -> Content tab -> Sync Connect Timeout - > 60
- Verification done with tfm-rubygem-katello-4.3.0.31-1.el7sat.noarch version

# rpm -qa|grep tfm-rubygem-katello
tfm-rubygem-katello-4.3.0.31-1.el7sat.noarch

- didn't see any timeout-related issue in the large repository sync after the upgrade.
Comment 12 errata-xmlrpc 2022-07-05 14:32:15 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.11 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-2022:5498