Bug 79387

Summary: Installer terminated with unhandeled exception error
Product: [Retired] Red Hat Linux Reporter: Nimitt <nimitt>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-12-11 04:13:10 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 Nimitt 2002-12-11 04:13:03 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
During the initial install phase I had selected a lot of packages to be 
installed.  Unfortunately there was not enough space on the allocated hard disk 
to install all of them

But instead of not prompting me about the same, anaconda simply crashed by 
informing that there was an unhandeled exception.

This needs to be looked into.  I suggest that either during the package 
selection phase itself there be a check with respect to the hard disk space 
available and the install size of the packages selected.

Regards,
Nimitt

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


How reproducible:
Always

Steps to Reproduce:
1. Start RHL install text or graphics will not make difference
2. Create a small / say 1024MB
3. Select packages of install size greater than 1024MB, anaconda will crash
	

Actual Results:  anaconda crashes and the installation is terminated.

Expected Results:  anaconda should report that not enough space is available 
for installation and that some packages should be deselected.

Additional info:

Comment 1 Michael Fulbright 2002-12-11 04:19:47 UTC

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