Red Hat Bugzilla – Bug 448851
yum dependency failures upgrading from 5.1 to 5.2 via Satellite
Last modified: 2008-12-23 12:01:11 EST
!! Also see SR #1830866 !!
Description of problem:
Recently updated our Satellite Server from 5.0.1 to 5.0.2. Now on some RHEL5.1
machines when an attempt to update them to 5.2 via yum (yum update) is done I
see strange dependency errors often times resulting in an endless loop.
Version-Release number of selected component (if applicable):
Satellite Server 5.0.2
Most of the time?
Steps to Reproduce:
1. Run 'yum update' on RHEL 5.1 client attached to RHN Satellite Server
Dependency loop or failures.
Dependencies solved and successful update.
I see requirements such as "iptables = 1.3.5-0 for package: iptables-ipv6".
See these mailing list threads:
Could my Satellite be giving out bad metadata?
I will attach two yum logs (one verbose and one not).
Created attachment 307007 [details]
yum -v -d 8 update
Created attachment 307008 [details]
there were some metadata for few packages with deps in 5.0.2. It could possibly
be some outdated cache that might be causing this. Try the following and see if
it still happens:
on Sat Server:
* rm -rf /var/cache/rhn/repomd*
* yum clean all
* yum update
This might timeout initially until the yum cache is regenerated on the server.
So watch for that as well.
Let me know if this helps.
Also want to mention, after "yum clean all" on the clients check your
/var/cache/yum/ and see if everything is cleaned up. If not nuke that stale data
with rm -rf /var/cache/yum/* . then run your yum update or rhn_check
This seems to have worked. After a yum clean all there was still data in the
local yum cache, but I cleared that out. The update is now proceeding and there
were no loops or apparent issues with the metadata after it regenerated.
I'll pass this along to the other places I posted; might be a good kbase article
if it doesn't already exist.
Should the Satellite have wiped its own metadata during the 5.0.1 to 5.0.2
upgrade process? Wonder how this happened.
Unfortunately we did not document this well in the Release Notes. But, the "yum clean all" should fix this situation.
*** This bug has been marked as a duplicate of bug 444878 ***