Bug 125898

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040518 Firefox/0.8

Description of problem:
The cron script for yum(yum.cron) never cleans up old rpms from
previous upgrades.  This causes /var partitions to fill up over time
causing some applications that use /var to stop working in such a way
that you dont know why they dont work anymore.

yum clean should be put into the cron script right after an upgrade so
that old rpms and headers that are not usable anymore are cleaned up.

If you think that some people might not want that for some reason then
make it a config setting in /etc/sysconfig/yum.  I am going to
recommend the same thing for setting the debug
level(/etc/sysconfig/yum) for the yum.cron script since I like to get
cron.daily output when a package gets updated(I set -d to 1).

Version-Release number of selected component (if applicable):
yum-2.0.7-1.1

How reproducible:
Always

Steps to Reproduce:
1. enable yum.cron daily script by running 'chkconfig yum on' and then
service yum start both as root.
2. Wait until an update is available and the cron job runs the next night.
3. Look at the /var/cache/yum and see that the rpm file is still there
even though it is already updated.


Actual Results:  var started filling up

Expected Results:  yum cron script should have cleaned up the updated
rpm by running yum clean after it ran yum update.

Additional info:

This is an important update because some people have 500 to 800 meg
var partitions that can fill up and cause all kinds of problems with
applications and services.