Bug 464855 - Anaconda crash at the end of F10-beta installation
Summary: Anaconda crash at the end of F10-beta installation
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 464894 465380 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-30 20:54 UTC by Didier
Modified: 2008-10-03 16:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-01 15:27:33 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
anaconda traceback (183.59 KB, text/plain)
2008-09-30 20:54 UTC, Didier 		no flags Details
View All

Description Didier 2008-09-30 20:54:40 UTC 
Created attachment 318123 [details]
anaconda traceback

Description of problem:

Anaconda crashes when writing /root/anaconda-ks.cfg


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

F10-beta


How reproducible:

Only tried once : installer exits, but freshly installed F10-beta system boots up fine afterwards.


Steps to Reproduce:
1. Start installation process (in this case, HD installation)
2. Default install (productivity + development)
3.
  
Actual results:

At the end of the installation, anaconda crashes and leaves an empty /root/anaconda-ks.cfg.


Expected results:

Correctly written anaconda-ks.cfg en nice slick restart. :)


Additional info:

See attached traceback.
Comment 1 Chris Lumens 2008-10-01 15:21:33 UTC 
*** Bug 464894 has been marked as a duplicate of this bug. ***
Comment 2 Chris Lumens 2008-10-01 15:27:33 UTC 
This will be fixed in the next build of anaconda.  Thanks for the report.
Comment 3 Chris Lumens 2008-10-03 14:08:03 UTC 
*** Bug 465380 has been marked as a duplicate of this bug. ***
Comment 4 Tom Horsley 2008-10-03 16:39:13 UTC 
Apparently, it did almost everything. I just tried booting the
partition I installed on, and the normal firstboot screen came up
and system appeared to be OK.
Note You need to log in before you can comment on or make changes to this bug.