Red Hat Bugzilla – Bug 1009578
RHEL 5 custom content without a FEED is not consumable by RHEL 5 clients
Last modified: 2017-02-23 16:19:36 EST
Description of problem:
based on https://github.com/Katello/katello/issues/2937 and verified myself
RHEL 5 content is not installable from a rhel 5 client.
Steps to Reproduce:
1. Sync a rhel 5 repo
2. Subscribe a system to it
3. Try to install some content
https://HOST/pulp/repos/ACME_Corporation/Library/content/dist/rhel/server/5/5.7/i386/resilientstorage/os/repodata/ce654caa186d0618cbc7fe0d64201e3b569cc683e88c743f8415df3866b0d853-primary.sqlite.bz2: [Errno -3]
Error performing checksum
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
I think there are two options:
In satellite 5/spacewalk, there was a checksum option added to repo creation that allowed the user to select what checksum they wanted. Do something similar to that.
Do what you suggest and fetch part of the repo to try to determine. I think we might eventually want some sort of override to give the user to override what checksum is being used.
Either way i'm good with moving off of mdp2
moving off MDP2
if we could fetch and determine that would be ideal but having a flag where you could force it would work too.
We did resolve some issues around this in Sat6 Beta and you are able to sync and consume RHEL5 content.
We need to ensure that bare repos with only RHEL5 sha1 RPMs uploaded via the API/UI will be able to produce sha1 repodata.
I'll test this out and see the state of this bug.
Connecting redmine issue http://projects.theforeman.org/issues/4056 from this bug
The changes mentioned in comment #6 were addressed as part of bug 1127402.
Moving to POST since upstream bug http://projects.theforeman.org/issues/4056 has been closed
Applied in changeset commit:katello|ed840853bc332a2fac1c2f8f93b6831a7e22dcf2.
# rpm -qa | grep foreman
Sync a rhel 5 repo
Subscribe a system to it and installed some content
This bug is slated to be released with Satellite 6.1.
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.