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 2053723 - Large repo sync failed with "Katello::Errors::Pulp3Error: Response payload is not completed"
Summary: Large repo sync failed with "Katello::Errors::Pulp3Error: Response payload is...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.10.3
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-11 20:35 UTC by Brad Buckingham
Modified: 2022-05-12 19:43 UTC (History)
13 users (show)

Fixed In Version: python3-pulpcore-3.14.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2033174
Environment:
Last Closed: 2022-03-08 21:26:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulpcore pull 1807 0 None Merged Retry downloads on checksum mismatch 2022-02-11 20:36:08 UTC
Github pulp pulpcore pull 1851 0 None Merged Fix retry logic of partially downloaded files 2022-02-11 20:36:08 UTC
Github pulp pulpcore pull 2122 0 None Merged Reset size and digests when retrying downloads 2022-02-11 20:36:08 UTC
Pulp Redmine 9667 0 None None None 2022-02-11 20:36:08 UTC
Red Hat Knowledge Base (Solution) 6596191 0 None None None 2022-02-11 20:36:08 UTC
Red Hat Product Errata RHSA-2022:0790 0 None None None 2022-03-08 21:26:23 UTC

Comment 3 Lai 2022-02-23 22:07:47 UTC 
Steps to retest

1. install 6.10 on a slow machine
2. syncing RHEL7 server repo

Expected:
Syncing should be successful

Actual:
Syncing is successful

Additional note:
To reproduce this was a little difficult because our VMs meet the minimum systems requirement, but we can't make it "slower" to see that the fix works.  Instead, I have spun up 2 machines (6.9 and 6.10.3).  I set the download-concurrency to 19 and 15 respectively.  Then perform the sync of the repo.

I have found that the 6.9 does consume more memories while the 6.10.3 one consume less, which you can see below.  I think this is sufficient in testing that the issue is resolved.

6.9.z
MemTotal:       20379856 kB
MemFree:          178856 kB
MemAvailable:    2871192 kB
 
 
6.10.3
MemTotal:       20379856 kB
MemFree:         1590204 kB
MemAvailable:    5125632 kB

Verified on 6.10.3 snap 2 with tfm-rubygem-pulpcore_client-3.14.1-1.el7sat.noarch
Comment 12 errata-xmlrpc 2022-03-08 21:26:16 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 (Low: Satellite 6.10.3 Async Bug Fix Update), 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:0790
Note You need to log in before you can comment on or make changes to this bug.