Bug 448851
Summary: | yum dependency failures upgrading from 5.1 to 5.2 via Satellite | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Ray Van Dolson <rvandolson> | ||||||
Component: | Client | Assignee: | Pradeep Kilambi <pkilambi> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Brandon Perkins <bperkins> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 502 | CC: | james.antill, jjneely, k.georgiou | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2008-12-23 17:01:11 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Ray Van Dolson
2008-05-29 02:30:58 UTC
Created attachment 307007 [details]
yum -v -d 8 update
Created attachment 307008 [details]
yum update
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* on Client: * 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. Thanks! 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 *** |