Bug 431776 - Installing on VMWare Workstation 5.5 VM, Anaconda crashes after partitioning
Summary: Installing on VMWare Workstation 5.5 VM, Anaconda crashes after partitioning
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2008-02-06 21:48 UTC by Joe McDonagh
Modified: 2008-02-07 17:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-07 17:48:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Saved Exception Report (361.24 KB, text/plain)
2008-02-06 21:48 UTC, Joe McDonagh 		no flags Details
View All

Description Joe McDonagh 2008-02-06 21:48:24 UTC 
Description of problem:
Going through an install works all the way up until it is setting up the
partition layout and encryption. It formats the partitions, then the installer
borks and gets an uncaught exception. The report is attached. Unchecking the new
 encryption feature didn't fix it.

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

How reproducible:
Every time

Steps to Reproduce:
1. Boot up the virtual machine in VMware Workstation 5.5.5 with 8 GB IDE virtual
drive, start install.
2. Next through everything (except I disabled ipv6).
3. Death.
  
Actual results:
See #3 in "Steps to Reproduce"

Expected results:
I installed with Rawhide on a non VM the other day, so I expected it to be like
that.

Additional info:
Comment 1 Joe McDonagh 2008-02-06 21:48:24 UTC 
Created attachment 294156 [details]
Saved Exception Report
Comment 2 Joe McDonagh 2008-02-07 15:21:39 UTC 
Same thing on VMware Server 1.0.4
Comment 3 Jeremy Katz 2008-02-07 15:33:26 UTC 
It happens on all installs and is caused by the rescue mode encrypted device support
Comment 4 David Lehman 2008-02-07 17:48:57 UTC 
A fix for this should appear in tomorrow's tree.
Note You need to log in before you can comment on or make changes to this bug.