Bug 876916

Created attachment 645544 [details]
anaconda screenshot

Sorry, the attachment in the description is not fully related to the reproducer. This one is. Please see this one and disregard the previous one.

The number for the required disk space is only for the software selection. It does not include the amount of swap space that would be allocated by automatic partitioning: Bug 876091, Comment 2.

Bug 876091 - Can not use free space to partition

In order to dupe, I'd first want to know how much swap space anaconda wanted to make.  Can you check in /tmp/anaconda.log and/or /tmp/storage.log?

Chris, all my VMs have 1.5 GB RAM, so anaconda most definitely wanted to create 3 GB of swap. The numbers in the screenshot match that: 2.67 GB + 3 GB > 5.47 GB

If you need exact logs, I can reproduce it fully and upload them here. But I'm pretty sure the proposed swap was 3 GB in size.

Discussed at 2012-12-19 NTH review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-19/f18final-blocker-review-6.2012-12-19-17.02.log.txt . Accepted as NTH - it's always useful to refine the minimum space detection - though if the fix is too big / risky we shouldn't pull it - please let us know if it looks like being a messy fix.

<bcl> adamw: that one clearly needs logs.

so we do need to provide precise logs, kamil. If I find time I might try to reproduce this and do it, if you don't get around to it first.

Created attachment 666567 [details]
*the screen* in 18.37.5

Created attachment 666568 [details]
18.37.5 anaconda.log

Created attachment 666569 [details]
18.37.5 storage.log

The red text in comment #7 is unrelated to this bug, just an improvement suggestion that really hits users' eyes. But the numbers are wrong similarly to the previous example - "requires 3.43 GB", "5.47 GB free", "you don't have enough space".

The same problem is in anaconda 19.8.

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

I hit this _very_ confusing issue when I installed to a VM.
By default virt-manager uses 8G disk images for VM storage,

With Fedora 19 requiring 4.5G and requiring 2G RAM VMs (4G swap I suppose),
we hit the issue easily.

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Given the fix for bug 853636 is now committed, can someone please re-test this bug report too?  Thanks.

Created attachment 739378 [details]
F19 anaconda screenshot

The issue seems to persist.

(In reply to comment #16)
To clarify, this is F19 Alpha with anaconda 19.20-1. Again, it claims it needs 3.7 GB, 5.11 GB is free, but it says there is not enough space available.

Created attachment 813299 [details]
20.25 first space dialog

With Anaconda 20.25 (F20 Beta TC4), the initial dialog claims that I need 2.92 GB of space. After I claim 3.2 GB free, I'm told that it's not sufficient and the same dialog claims that I need 3.95 GB of space.

The swap is counted only in the second attempt.

Created attachment 813300 [details]
20.25 second space dialog

Created attachment 820971 [details]
anaconda 20.25.6

A funny story with anaconda 20.25.6. Still not counting correctly.

Setting priority high since you hit this often (like install to default VM for e.g.)

Setting severity high since it's very confusing and blocks install

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Seems to work well in Fedora 22.