RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

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.

We need to fix this in active z-streams as well

Proposed solution:

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

Fix available in upstream ...

spacewalk.git: f53a791847105cf422f9fbb41dcb41eeb018c6be