Bug 534052

Summary: Preupgrade should check for sufficient disk space in advance
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: preupgradeAssignee: Seth Vidal <skvidal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-10 15:14:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
error message
none
logs none

Description Kamil Páral 2009-11-10 11:35:07 UTC
Created attachment 368368 [details]
error message

Description of problem:
My preupgrade failed because of insufficient disk space on /boot. Couldn't preupgrade check for sufficient disk space in advance, when started using preupgrade command from running environment?

Version-Release number of selected component (if applicable):
anaconda 12.46
preupgrade-1.1.2-1.fc11.noarch

How reproducible:
tried once
 
Actual results:
low disk space is announced after downloading all packages and running the upgrade itself

Expected results:
low disk space is announced right after running preupgrade command in the graphical dialog

Comment 1 Kamil Páral 2009-11-10 11:35:30 UTC
Created attachment 368369 [details]
logs

Comment 2 Kamil Páral 2009-11-10 11:40:12 UTC
I was preupgrading from Fedora 11 to Rawhide (soon to be released as F12).

Comment 3 Will Woods 2009-11-10 15:11:14 UTC
It *does* check for sufficient space, but anaconda uses a different algorithm - it attempts an RPM transaction test, which also does a check for available space.

Preupgrade used the same check as anaconda in the past, but it took several minutes to run and still failed to notice when there was insufficient room on /boot.

Comment 4 Will Woods 2009-11-10 15:14:02 UTC

*** This bug has been marked as a duplicate of bug 530541 ***