Bug 316551

Summary: Unhandled exception after creating lvm configuration
Product: [Fedora] Fedora Reporter: Sven Lankes <sven>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8   
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: 2007-10-05 15:35:26 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:
Attachments:
Description Flags
Anaconda-Log of the failed setup none

Description Sven Lankes 2007-10-03 09:10:15 UTC 
Description of problem:

F8T2 anaconda (started from a rescue-cd) shows an unhandled exception
error after configuring lvm.

How reproducible:

Steps to Reproduce:
1. start installation
2. create lvm vg, swap-lv, root-lv
3. choose continue

Actual results:

Dialog-Box showing an unexpected error.

Expected results:

A successful F8T2 install

Additional info:

This is on a samsung Q35-notebook (intel platform, c2d). To actually
get the rescue-cd to boot I had to append noapic acpi=off to the 
kernel commandline.

The 250 GB disk has a 10 GB XP Install on it. I want to install F8T2 
into a LVM-LV that I created using anaconda. After creating the VG and a
LV for swap and one for root anaconda showed an unhandled exception 
dialog.
Comment 1 Sven Lankes 2007-10-03 09:10:15 UTC 
Created attachment 214421 [details]
Anaconda-Log of the failed setup
Comment 2 Sven Lankes 2007-10-03 09:28:10 UTC 
I just retried the installation. This time instead of creating the lvm-setup
from scratch, I had anaconda create it and I only customized it then. That way
the installations works fine. 

I noticed that I didn't create a non-lvm /boot-Partition in my first try - but
even if that is the reason for the error I'd still say that the but-report is valid.
Comment 3 Jeremy Katz 2007-10-05 15:35:26 UTC 
Okay, I see what's going on here.  Fixed in CVS