Bug 951899

Summary: Starting anaconda fails with unknown error
Product: [Fedora] Fedora Reporter: Pavel Rosenboim <pavel1r>
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: rawhideCC: anaconda-maint-list, 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: 2013-04-15 12:59:48 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
anaconda log
none
traceback
none
program.log
none
storage.log none

Description Pavel Rosenboim 2013-04-14 08:32:45 UTC
Created attachment 735549 [details]
anaconda log

Description of problem:
I'm trying to install F19 Alpha RC2. As soon as anaconda starts it
produces a dialog saying "An unknown error has occured. This program
encountered an unknown error. You may report the bug below or quit the
program". After that it becomes stuck and does not allow to press "More info" or "Report bug". Happens with both live cd and network install cd.

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


How reproducible:
Always

Steps to Reproduce:
1. start installing F19 Alpha RC2 from either live dvd or netinstall

Additional info:

Comment 1 Pavel Rosenboim 2013-04-14 08:33:38 UTC
Created attachment 735550 [details]
traceback

Comment 2 Pavel Rosenboim 2013-04-14 08:34:35 UTC
Created attachment 735551 [details]
program.log

Comment 3 Pavel Rosenboim 2013-04-14 08:34:53 UTC
Created attachment 735552 [details]
storage.log

Comment 4 Chris Lumens 2013-04-15 12:59:48 UTC

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