Bug 1970095

Summary: Syncing a large repo from CDN with Download Policy set to "Immediate" fails
Product: Red Hat Satellite Reporter: Stephen Wadeley <swadeley>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: dalley, ggainey, jsherril, osousa, pcreech, rchan, ttereshc
Target Milestone: 6.10.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-pulpcore-3.14.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:11:38 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 Stephen Wadeley 2021-06-09 19:47:30 UTC 
Description of problem:

Syncing a large repo from CDN with
 Download Policy set to "Immediate" fails



Version-Release number of selected component (if applicable):
6.10.0-3.0
python3-pulpcore-3.11.0-1.el7pc.noarch

How reproducible:
Almost every time on a large repo such as rhel7 server


Steps to Reproduce:
1. Install a manifest
2. Enable rhel-7-server-rpms
3. Go to Products > Red Hat Enterprise Linux Server > Repositories > Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server 
4. Download Policy set to "Immediate"
5. Select Action > Sync Now

Actual results:
Task stays in Pending
If you click through for more details you will see error
 'Response payload is not completed'


Expected results:
Repo should sync

Additional info:

Tried again with "hammer repository update  --id=X --download-concurrency=2" but it still failed.
Comment 1 Justin Sherrill 2021-06-09 19:53:02 UTC 
This likely should be hooked up with https://pulp.plan.io/issues/8881

but https://pulp.plan.io/issues/8878 also describes this issue.
Comment 2 pulp-infra@redhat.com 2021-06-21 15:08:03 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2021-06-21 15:08:06 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2021-06-21 16:13:52 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 6 pulp-infra@redhat.com 2021-07-01 15:08:29 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 7 Tanya Tereshchenko 2021-07-02 09:28:15 UTC 
Fixed in pulpcore 3.14.0.
Comment 11 pulp-infra@redhat.com 2021-07-26 16:11:07 UTC 
Requesting needsinfo from upstream developer dalley because the 'FailedQA' flag is set.
Comment 13 pulp-infra@redhat.com 2021-07-26 17:16:13 UTC 
Requesting needsinfo from upstream developer dalley because the 'FailedQA' flag is set.
Comment 15 pulp-infra@redhat.com 2021-07-26 18:08:57 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 16 pulp-infra@redhat.com 2021-07-26 18:08:58 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 20 errata-xmlrpc 2021-11-16 14:11:38 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