Red Hat Bugzilla – Bug 656746
RHN proxy 5.4: rhn_package_manager unable to upload packages due to md5sum error
Last modified: 2010-12-16 09:58:59 EST
Description of problem:
After customer updates RHN Proxy server to version 5.4 the following occurs:
[root@cyclops RPMS]# rhn_package_manager -c i386-client-5.5 i686/kmod-openafs-*2.6.18-194.26.1*
Red Hat Network username:
Red Hat Network password:
The package's md5 digest has not been specified
Error Class Code: 50
Error Class Info: Invalid information uploaded to the server
An error has occurred while processing your request. If this problem
persists please enter a bug report at bugzilla.redhat.com.
If you choose to submit the bug report, please be sure to include
details of what you were trying to do when this error occurred and
details on how to reproduce this problem.
However the openafs kmod packages were produced on a fully updated rhel5.5 system and the md5 digest exists in the rpm.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHN Proxy 5.4 server, register against Hosted.
2. Try to upload custom pkg to custom channel (see example above).
Failure. "The package's md5 digest has not been specified" error (see above)
Success with no errors.
This is not seen with RHN Proxy server against 5.4 Satellite.
Additionally, if -v flag is used the actions fail even earlier. Bug 656753 has been filed separately.
We do not send md5sum header. We now send checksum and checksum type, which hosted could not handle.
I override rhn_package_manager to send md5 checksum as well.
cherrypicked to satellite.git as commits:
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, package uploads from the rhn_package_manager tool failed on RHN Proxy Server 5.4 with the parent http://rhn.redhat.com/. With this update, the uploading process succeeds.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.