Bug 217923

Summary:	Anaconda does not alert you that the installation is too big for the parition before installing
Product:	[Fedora] Fedora	Reporter:	kentphilip
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6
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:	2007-02-28 18:22:56 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:

Description kentphilip 2006-11-30 19:43:29 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30)

Description of problem:
Anaconda does not alert you on the size of the install (like it did in previous versions, when it embedded system-config-packages into the screen) vs the ammount of space you have to install on, so you do not know if the install is too big. Plus, if the install is too big, it just fails in file copy, you are not told beforehand, so you have to reboot the disk and ajust the settings (and if it fails again, you will probably be annoyed by now).

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


How reproducible:
Always


Steps to Reproduce:
1. Boot the install CD
2. Go through
3. Begin the install.

Actual Results:
Install gives no alert on required disk space or if disk is full.

Expected Results:
It should tell you how much disk space the install takes vs the ammount you have on the disk/partition, and alert you if the install is too big.

Additional info:

Comment 1 Chris Lumens 2007-02-28 18:22:56 UTC

Due to doing dependency resolution at package selection time instead of having
pre-calculated dependencies, we can no longer offer a size estimate on the
package selection screen.  However, we do check that the size of the installed
package set will fit in the amount of space you've partitioned up.  This check
is pretty good, but not foolproof - for instance, you can easily confuse it by
splitting your free space up into a variety of partitions for things like /var
and /usr.  The package headers don't give us fine-grained enough information to
handle that situation, so you will still have to have a large enough / partition.

I have just verified that this check is being performed and does work.