|Summary:||Yum will not show available updates|
|Product:||[Fedora] Fedora||Reporter:||Robert Staaf <rstaaf>|
|Component:||yum-utils||Assignee:||Luke Macken <lmacken>|
|Status:||CLOSED NOTABUG||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||7||CC:||init, james.antill, pfrields|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-03-13 13:39:17 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Robert Staaf 2007-06-19 23:53:56 UTC
Description of problem: I noticed yesterday after receiving the announcements from fedora_package_announce that my machine was not showing any updates through Pup so I check directly via Yum, same result. I ran yum clean all and the updates then showed as they should and I updated and forgot about it. Today there were another round of updates and again my machine was not showing any updates even though several were applicable to my installation. This time I did an selinux relabel and again the updates showed as they should have and I was able to update my machine.
Comment 1 Jeremy Katz 2007-06-20 15:14:08 UTC
Are you pointing explicitly at a mirror or just using the default mirrorlist setup?
Comment 2 Keith Dixon 2007-07-04 09:24:03 UTC
I have had precisely the same problem with no updates since 26JUN07 until this morning after doing "yum clean all". I suspect the fastestmirror plugin as /var/cache/yum/timedhosts.txt is also deleted by "yum clean all". If the fastest mirror was not being synced correctly that may explain this behaviour. I have not, however, tried the selinux relable as the problem has not yet recurred. Robert, do you have the fastestmirror plugin installed? $ rpm -q yum-fastestmirror yum-fastestmirror-1.1.5-1.fc7
Comment 3 Ingemar Nilsson 2007-08-09 16:07:15 UTC
I have also had the same problem. I'm using the default mirrorlist setup, and I have the fastestmirror plugin installed. A "yum clean all" usually, but not always, solves the problem. Sometimes, I had to do a "yum clean all" followed by a "yum --noplugins update" to actually get any updates.
Comment 4 Luke Macken 2007-09-15 16:05:20 UTC
It sounds like you could be hitting an out of sync mirror each time.. Try applying the following patch to /usr/lib/yum-plugins/fastestmirror.py --- a/plugins/fastestmirror/fastestmirror.py +++ b/plugins/fastestmirror/fastestmirror.py @@ -82,6 +82,7 @@ def postreposetup_hook(conduit): repo.failovermethod = 'priority' repo.check() repo.setupGrab() + print "repomirrors[%s] = %s" % (str(repo), repomirrors[str(repo)]) if not loadcache: write_timedhosts() This will make fastestmirror spit out the mirrorlist for each repository. This way you'll be able to see which mirror you are hitting, and will then be able to determine if it is out of sync or not. Other than an out of sync mirror, I can't think of anything that fastestmirror is doing that would prevent you from getting updates.
Comment 5 Ingemar Nilsson 2007-09-21 13:43:50 UTC
I added the line to fastestmirror.py, but it outputs a very long list of mirrors. Should I manually check if they are out of sync when the problem occurs next time? That would take an entire day, time that I may have to spare. Or is there a way to check mirror sync using some automated tool?
Comment 6 Luke Macken 2007-09-21 16:28:06 UTC
The first entry of each list is the mirror that your client uses *first*, which is possibly out of sync. You could check by hand if that mirror contains the updates you are looking for, or look at the repodata. I've been thinking about it, and it could also be that the mirrormanager is sending you a list of mirrors (lets say mirror A is out-of-sync and has been removed from this list). Fastestmirror doesn't care and just loads the cached hosts file as it is, even if A is at the top of the list. I think if fastestmirror somehow was able to prune out non-existent mirrorlist entries from the cache, it may fix some problems -- considering the mirrormanager goes out of it's way to keep things in check.
Comment 7 Ingemar Nilsson 2007-10-02 11:11:48 UTC
Today, when updating my system, the problem occurred again. The complaint was about missing dependency kernel-xyz-85.fc7 (xyz = the details are irrelevant) for kmod-ntfs-xyz-85.fc7. The problem was that the latest kernel was xyz.91.fc7 while the latest kmod-ntfs was xyz.85.fc7. I checked the first mirror (mirror.atrpms.net), and sure, it hadn't got the latest kmod-ntfs. Then I decided to do a "yum clean all" to see if fastestmirror would select another mirror, and it did. This mirror had the latest kmod-ntfs, and the update worked as expected. Note though that in this case, the failing mirror was for livna, which don't use a mirrormanager, but rather a static list of mirrors in the repo file.
Comment 8 Seth Vidal 2008-03-13 13:39:17 UTC
Unless I'm misreading this sounds like notabug. Out-of-sync mirrors are pretty much impossible to fix in fastest-mirror.