Bug 621101

Summary: Anaconda crash when trying to install F14-Alpha-TC2 (x86_64)
Product: [Fedora] Fedora Reporter: Joachim Backes <joachim.backes>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 14CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
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: 2010-08-04 14:11:24 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:
Attachments:
Description Flags
anaconda traceback none

Description Joachim Backes 2010-08-04 09:23:39 UTC 
Description of problem:
I tried to install F14-Alpha-TC2 in a pre-xisting ext3 formatted partition (should be used as /). If having selected this partition and trying to proceed, anacanoda crashes with a traceback (see attachment).

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

14.14
How reproducible:
always

Steps to Reproduce:
1.Boot from the DVD and select a pre-exististing ext3 ext3 formatted partition
  as target for /.
2.
3.
  
Actual results:
crash

Expected results:
preeds with install

Additional info:
Comment 1 Joachim Backes 2010-08-04 09:24:39 UTC 
Created attachment 436477 [details]
anaconda traceback
Comment 2 Joachim Backes 2010-08-04 09:27:34 UTC 
Remark: Trying to install F14 into a free logical partition (not formatted) fails too (I'm sorry, no tb available), indepently from the filesystem type to be created.
Comment 3 Chris Lumens 2010-08-04 14:11:24 UTC 
In the future, please attach tracebacks as non-compressed plain-text files, not XML blobs.  Those are much harder to read, and compressed files are not easily searchable by bugzilla.

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