Description of problem: When performing a text install and choosing autopartition, manual partition acts in a non-intuitive way. If you select "Fill all available space:" and deselect the other partition size options, an error returns: Invalid Entry for Partition Size Must specify a value. One would assume that if you are selecting an option to fill the partition with all available space, it would not be necessary to define any sizing. As it so happens, if you put a 1 in the "Size (MB)" field, it will accept that and go forward, creating a partition which uses all available space. Putting in a 0 (zero) causes anaconda to crash. See the follow-on bug report for the traceback. Version-Release number of selected component (if applicable): RHEL 3 anaconda as ships with RHEL 3 diskdruid? as ships with RHEL 3 How reproducible: Always. Steps to Reproduce: 1. Start a text install of RHEL 3, choose autopartitioning 2. Manually tweak the offered partition, creating a new partition which takes up all available space 3. Set the "Size (MB)" to 0 (zero) to crash, or to nothing to cause it to error in an unexpected fashion. Actual results: Crash or apparent inability to set a dynamic partition creating size without specifying a static vallue. Expected results: Nothing crashes or complains when the "Size (MB)" filed is filled with 0 or left blank. Additional info: See follow-up traceback.
Created attachment 95540 [details] anaconda traceback dump This was the traceback generated when the value of 0 was entered into the "Size (MB)" field.
Created attachment 95541 [details] anaconda traceback dump This was the traceback generated when the value of 0 was entered into the "Size (MB)" field.
Created attachment 95542 [details] syslog of system for time around the anaconda crash. This was the syslog for the install session. Going to try to submit this without sending it twice. :/
Don't do that then :-)
*** Bug 108162 has been marked as a duplicate of this bug. ***
Fixed, thanks for the machine access.
Oops, last comment was meant for another bug. I've actually fixed this now on HEAD of CVS. It's a candidate to backport for a Taroon update at some point, but it's been this way forever, so I don't know how high of a priority it is to actually do so.
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-195.html