Description of problem: cachecookie files are not being cleaned as part of clean operations. as a result the next run of yum can't find the repodata and no longer attempts to contact a server to refresh. Version-Release number of selected component (if applicable): 2.4.1-1 How reproducible: Steps to Reproduce: 1. install 2.4.1-1 2. yum check-update to see mirror contact and to create the cookie files 3. yum check-update to see the new caching prevents contacting a mirror 4. yum clean all 5. yum check-update instant death. 6. remove all cachecookie files in the cache directory tree 7. yum check-update works as expected Additional info: what is the default length of time till cookies expire? how do i configure that length of time? and how do i turn this feature off?
hyperbole, much? answers: - the clean command should kill off this cookie, I agree - I'll look into it - it's documented in the man page: metadata_expire=0 will disable the caching - the current time is 8 hours and then it goes away. It can be set per-repo, of course, so for the rapidly changing repos you can set it low and for the uncommonly changing repos you can leave it alone.
Created attachment 121703 [details] Patch to clean cookies along with metadata Patch as suggested by Seth on yum-devel: - clean the cookies on 'yum clean metadata' instead of separate operation - force refresh of cookies on 'yum makecache'
Panu, check it in. And Jeremy, if you want apply this as a patch to fedora's yum package for 2.4.1 and give it another test run in updates-testing, okay?
*** Bug 174864 has been marked as a duplicate of this bug. ***
*** Bug 174938 has been marked as a duplicate of this bug. ***
Applied Panu's patch as well as the change to bump the default cache time to 30 minutes for FC4 updates and devel
*** Bug 175076 has been marked as a duplicate of this bug. ***