Bug 962831

Summary: Installation on dmraid fails when there are existing partitions
Product: [Fedora] Fedora Reporter: Tim Flink <tflink>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-08 21:39:20 UTC Type: Bug
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
traceback from install
none
anaconda storage.log
none
anaconda program.log
none
anaconda storage.state
none
anaconda.log none

Description Tim Flink 2013-05-14 14:25:20 UTC
Created attachment 747718 [details]
traceback from install

I did an install of F19 beta TC4 i386 onto a machine with a mdraid array.

When I went through the configuration process, I ended up in the reclamation dialog but the array showed up as completely empty.

I got a traceback shortly after starting the install but libreport duped it to #961165 and #960271 and I am filing a new bug as directed in c30.

Comment 1 Tim Flink 2013-05-14 14:26:20 UTC
Created attachment 747719 [details]
anaconda storage.log

Comment 2 Tim Flink 2013-05-14 14:26:51 UTC
Created attachment 747720 [details]
anaconda program.log

Comment 3 Tim Flink 2013-05-14 14:27:17 UTC
Created attachment 747721 [details]
anaconda storage.state

Comment 4 Tim Flink 2013-05-14 14:28:00 UTC
Created attachment 747722 [details]
anaconda.log

Comment 5 David Lehman 2013-05-14 15:50:12 UTC
This should be fixed in bug 957188.

Comment 6 David Shea 2014-12-08 21:39:20 UTC
Closing per comment 5.

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