Hide Forgot
Description of problem: During kickstart repository sync pxeboot images [initrd.img and vmlinuz] are not downloading Pulp Logs : Mar 05 11:20:03 satellite.example.com pulp[50927]: pulp.server.controllers.repository:INFO: Download of /var/lib/pulp/content/units/distribution/43/68d01d22cef0f2a50c9bc17de7e77f3d4ebde5e7c1243bcd774bfed4bf3733/images/pxeboot/initrd.img failed: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing: incorrect header check',)). Mar 05 11:20:05 satellite.example.com pulp[50927]: pulp.server.controllers.repository:INFO: Download of /var/lib/pulp/content/units/distribution/43/68d01d22cef0f2a50c9bc17de7e77f3d4ebde5e7c1243bcd774bfed4bf3733/images/pxeboot/vmlinuz failed: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing: incorrect header check',)). How reproducible: Sometimes but not always
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Hi We are impacted by this bug, is there any ETA to release the fix for satellite 6.5?
Niloofar, we will work to include this in 6.5.3. If you would like to request a hotfix, please open a support case and we can likely get one created for you.
This hotfix applies to both the Satellite server and Capsules. Please ensure it is applied to both. *** Satellite 6.5.2 Hotfix Available *** 1) Download hf-1687801.tar from this bugzilla to your Satellite and Capsules 2) Install: tar xvf hf-1687801.tar rpm -Uvh *.rpm 3) restart: satellite-maintain service restart 4) resume operations
Created attachment 1603868 [details] hf-1687801.tar
This hotfix applies to both the Satellite server and Capsules. Please ensure it is applied to both. *** Satellite 6.4.4 Hotfix Available *** 1) Download hf-6.4.4-1687801.tar.gz from this bugzilla to your Satellite and Capsules 2) Install: tar xvf hf-6.4.4-1687801.tar.gz rpm -Uvh *.rpm 3) restart: satellite-maintain service restart 4) resume operations
Created attachment 1605133 [details] hf-6.4.4-1687801.tar.gz
Hey guys, we are affected from the same bug. Aug 21 11:11:38 SATELLITE pulp[11135]: pulp.server.controllers.repository:INFO: Download of /var/lib/pulp/content/units/distribution/53/fd9ee153454ae71208d2db4e6d83a50/images/pxeboot/vmlinuz failed: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing: incorrect header check',)). Aug 21 11:11:38 SATELLITE pulp[11135]: pulp.server.controllers.repository:INFO: Download of /var/lib/pulp/content/units/distribution/53/fd9ee153454ae71208d2db4e6d83a50/images/pxeboot/initrd.img failed: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing: incorrect header check',)). Aug 21 11:11:38 SATELLITE pulp[11135]: pulp.server.controllers.repository:INFO: Download of /var/lib/pulp/content/units/distribution/53/fd9ee153454ae71208d2db4e6d83a50/images/pxeboot/ d.img failed: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing: incorrect header check',)). Iam wondering how its possible for me to install a new system via Satellite (host bootdisk) without the necessary kernel/initrd!? Or does the satellite download the kernel/initrd to the directory and removes it after the ipxe-boot due to the 'incorrect header check'? Best regards, Dominic
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, 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-2019:3172