Bug 1423003

Summary: yum-rhn-plugin sending malformed request header
Product: Red Hat Enterprise Linux 6 Reporter: Grant Gainey <ggainey>
Component: yum-rhn-pluginAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.9CC: jhutar, jneedle, jreznik, mkolaja, tlavigne, tlestach, xdmoon
Target Milestone: rcKeywords: ZStream
Target Release: 6.9   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1423004 1423007 1425079 1425080 1425081 1425082 1425084 1425085 (view as bug list) Environment:
Last Closed: 2017-05-24 14:35:25 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: 1423004, 1423007, 1425079, 1425080, 1425081, 1425082, 1425084, 1425085    

Description Grant Gainey 2017-02-16 20:16:44 UTC
Description of problem:

The yum-rhn-plugin sends http-headers that are separated by only a newline, when the spec requires CRLF.

In the presence of an httpd which enforces the spec, this results in any attempt to update/install content returning

error was [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 400 Bad Request"

Version-Release number of selected component (if applicable):

The bug was introduced in yum-rhn-plugin-0.8.4-1. The problem was harmless until uncovered by fixes for httpd that tightened whitespace processing.

How reproducible:

See https://bugzilla.redhat.com/show_bug.cgi?id=1422518 for gory details. The net is, 'yum update a system that is talking to a satellite-5 whose httpd is at 2.2.15-60 or higher'.

Actual results:

error was [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 400 Bad Request"

Expected results:

successful install/update of packages.

Additional info:

This BZ is for getting the client-side fix in place for RHEL6, BZ#1422518 is for getting a workaround in place on the Satellite5 backend.

This needs to be fixed for RHEL6.9 if at all possible, in order to have the fix on the ISO and in kickstart trees.

Comment 1 Grant Gainey 2017-02-16 20:18:50 UTC
We need to fix this in active z-streams as well

Comment 3 Grant Gainey 2017-02-16 20:37:53 UTC
Proposed solution:

https://github.com/spacewalkproject/spacewalk/pull/506

Comment 4 Tomas Lestach 2017-02-20 08:16:30 UTC
Fix available in upstream ...

spacewalk.git: f53a791847105cf422f9fbb41dcb41eeb018c6be