The summary pretty much says it all, when one gets
a "not enough freespace dialog" in a textmode install and then presses ok,
the next thing that happens is a traceback.
For the traceback see:
Which is part of bug 591469, which is used for tracking the cause of (in this case wrongly) getting the not enough freespace dialog.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
anaconda 13.21.45 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/text.py", line 595, in run
(file, classNames) = stepToClasses[step]
File "/usr/bin/anaconda", line 1107, in <module>
I think all that's needed here is to cherry-pick 0982f94dc987adc3b6aa4634a3150a7ba01d8229.
Verified with build RHEL6.0-20100531.1, anaconda-13.21.48-1.el6. Following traceback is no longer displayed, user is able to "Write changes to disk" or "Go back".. There's another traceback after user selects "Write changes to disk", but it's different issue (bug 599484).
I'm closing this bug as VERIFIED.
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.