Description of problem:
If "yum update --downloadonly" is interrupted or fails during download for some reason (bad network, etc), it leaves its temp files behind. Unfortunately, when the command is run again, yum leaves these temp files in place rather than resuming them where it left off.
Worse, the temp files are never cleaned up. Even "yum clean all" ignores them, so the space is lost.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Do a yum update --downloadonly
2. Hit ctrl-C while it's mid download
3. Run yum update --downloadonly again
Various #####.tmp files left behind in /var/cache/yum
No leftover temp files.
This seems identical to (fixed) Fedora bug 1045806. Can that fix be applied to RHEL?
Commits for fixes related to this issue are located here:
Probably need both pulled in to fully correct the problem.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.