Bug 703820

Summary: yum upgrade fail : installing package needs disk space on / filesystem, but there's more available disk space than requested
Product: [Fedora] Fedora Reporter: Yann Droneaud <yann>
Component: yumAssignee: Seth Vidal <skvidal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: ffesti, james.antill, maxamillion, pmatilai, tla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-13 13:09:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
yum upgrade output
none
yum --verbose upgrade log
none
yum upgrade output none

Description Yann Droneaud 2011-05-11 10:36:59 UTC 
Description of problem:

Since "yum distro-sync" doesn't work after preupgrade from f14 to f15, see bug #703732, I'm trying to use "yum upgrade" instead, but it fails too, with error messages about missing disk space. It says the update will requires less than 800MBytes on root filesystem and fails. But root filesystem has 2.5GBytes available.

Something is wrong in the required space computation, or the error message is unclear.
Comment 1 Yann Droneaud 2011-05-11 10:40:16 UTC 
Created attachment 498250 [details]
yum upgrade output
Comment 2 Yann Droneaud 2011-05-11 10:42:11 UTC 
Created attachment 498252 [details]
yum --verbose upgrade log
Comment 3 Yann Droneaud 2011-05-13 11:23:47 UTC 
Created attachment 498747 [details]
yum upgrade output

Today it requires less disk space: 222MBytes, but it still fail to upgrade anything.
Comment 4 Panu Matilainen 2011-05-13 11:29:58 UTC 
The message might be a bit ambiguous, the "needs XX MB" just means the transaction would need that much /more/ free space than is available to complete. So not a bug really, just a slightly unclear error message.