Bug 1128160

Summary:	check free space before download
Product:	Red Hat Enterprise Linux 6	Reporter:	Petr Stodulka <pstodulk>
Component:	redhat-upgrade-tool	Assignee:	Michal Bocek <mbocek>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.5	CC:	jkurik, mlinden, phracek, ttomecek
Target Milestone:	rc	Keywords:	Extras
Target Release:	6.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-01 15:26:24 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:
Embargoed:

Description Petr Stodulka 2014-08-08 12:58:45 UTC

Description of problem:
redhat-upgrade-tool doesn't check available space for new packages before download. I think it should be checked when downloaded packages are nown.


Version-Release number of selected component (if applicable):
RHEL-6.5

How reproducible:
always

Steps to Reproduce:
1. fill sufficiently free space by some file
2. redhat-upgrade-tool --network 7.0 --instrepo \
   http://download.eng.brq.redhat.com/released/RHEL-7/7.0/Server/x86_64/os/

Actual results:
[....]
Downloading failed: Errors were encountered while downloading packages.
  2:texlive-pst-node-svn27799.1.25-32.el7.noarch: Insufficient space in download directory /var/tmp/system-upgrade/cmdline-instrepo/packages
    * free   0 
    * needed 39 k
[...]

Expected results:
Insufficiency free space for download ....

Comment 1 Petr Stodulka 2014-08-08 13:12:09 UTC

Version-Release number of component:
redhat-upgrade-tool-0.7.24-1.el6.noarch

Comment 2 David Shea 2015-10-30 20:07:31 UTC

*** Bug 1276577 has been marked as a duplicate of this bug. ***

Comment 4 Michal Bocek 2019-07-01 15:26:24 UTC

Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.