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.
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:
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.
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