Bug 1410234

Summary: yum update --downloadonly doesn't resume download, and leaves temp files behind
Product: Red Hat Enterprise Linux 7 Reporter: David Shaw <dshaw>
Component: yumAssignee: Michal Domonkos <mdomonko>
Status: CLOSED ERRATA QA Contact: Eva Mrakova <emrakova>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: cdonnell, dmach, emrakova, james.antill, jcastran, mdomonko, toneata
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: yum-3.4.3-162.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:13:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1477664, 1630909, 1630918    

Description David Shaw 2017-01-04 21:03:48 UTC
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):

yum-3.4.3-150

How reproducible:

Every time.

Steps to Reproduce:
1.  Do a yum update --downloadonly
2.  Hit ctrl-C while it's mid download
3.  Run yum update --downloadonly again

Actual results:

Various #####.tmp files left behind in /var/cache/yum

Expected results:

No leftover temp files.

Additional info:

This seems identical to (fixed) Fedora bug 1045806.  Can that fix be applied to RHEL?

Comment 13 errata-xmlrpc 2019-08-06 13:13:29 UTC
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.

https://access.redhat.com/errata/RHBA-2019:2286