Bug 431776

Summary: Installing on VMWare Workstation 5.5 VM, Anaconda crashes after partitioning
Product: [Fedora] Fedora Reporter: Joe McDonagh <jmcdonag>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: petersen
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-07 17:48:57 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:
Bug Depends On:    
Bug Blocks: 235706    
Attachments:
Description Flags
Saved Exception Report none

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.