Description of problem:
rhn_check events from 'packages.' namespace fail, when the caching file
(rhnplugin.repos) contains outdated information.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Register system with RHN Hosted to the base channel
2. # yum repolist
3. Register system with RHN Satellite without any channel
4. Schedule 'Update Package List' on RHN Satellite webui
5. # rhn_check -vv
Fatal error in Python code occured
yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: rhel-i386-server-5. Please verify its path and try again
rhn_check tool should not crash, even in case the rhnplugin.repos
contains outdated information.
Created attachment 523112 [details]
snippet from /var/log/up2date
Regression against earlier rhel5 releases (rhel5.5 and older).
Having this issue as well.
I've tried to manually clean up /var/cache/yum to force an update of the rhnplugin.repos but I am unable to get a usable rhnplugin.repo file.
Has anyone managed a work-around?
This is on RHEL6.1
(In reply to comment #5)
> This is on RHEL6.1
More debugging -- turning off SSL in /etc/sysconfig/rhn/update lets rhn_check succeed and everything else work as expected.
My issues appear to be duplicates of #692118 and corresponding Fedora bugs:
738566 - python-urlgrabber
738367 - yum
738568 - anaconda
Added RHTS keyword.
QA would like to have an automated test for this issue. Well, currently,
the issue might be exposed by our automation, when series of different
tests make a use of different channel sets. However, having separate test
for this issue, would be a preferred. That way, would would minimize the
risk that test cases gets lost by yum-clean-like workarounds.
Added qa_ack+ as well.
The issue has been already fixed by z-stream errata package
The issue has been addressed as a part of bug 734965 and bug 735282.
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.