ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001524ClearOSapp-base - Base Systempublic2014-01-21 08:252014-04-02 14:46
Reporteruser2 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version6.5.0 UpdatesFixed in Version6.5.0 Updates 
Summary0001524: Yum cache is still problematic
DescriptionWe still see reports of yum caching extremely old data. For example, a customer recently reported a cache that contained data that was at least 4 days old! In 6.5.0, the following parameter was added to yum.conf:

http_caching=packages

There's also the "metadata_expire" (defaults to 6 hours) and "mirrorlist_expire" parameters that might need to be shortened. That still doesn't explain the "4 days old" behavior. Perhaps it's related to skewed clocks at install time?
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
duplicate of 0001562closed user2 Yum cache is still problematic 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-01-21 08:25user2New Issue
2014-01-21 09:14user2Note Added: 0001134
2014-01-21 09:14user2Assigned To => user2
2014-01-21 09:14user2Statusnew => confirmed
2014-02-07 13:15user2Statusconfirmed => resolved
2014-02-07 13:15user2Fixed in Version => 6.5.0 Updates
2014-02-07 13:15user2Resolutionopen => fixed
2014-02-13 09:45user2Issue cloned: 0001562
2014-02-13 09:45user2Relationship addedduplicate of 0001562
2014-04-02 14:46user2Statusresolved => closed

Notes
(0001134)
user2   
2014-01-21 09:14   
Confirmed the clock skew.

1) Set metadata_expire=60
2) Run "yum repolist" to grab repo data
3) Set clock back a day
4) Run "yum repolist" after a few minutes... the cache is never purged.