Bug 495608 - Traceback while doing custom layout install with raid and encryption
Summary: Traceback while doing custom layout install with raid and encryption
Keywords:
Status: CLOSED DUPLICATE of bug 491729
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-14 02:38 UTC by Bruno Wolff III
Modified: 2009-04-17 13:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-17 13:50:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Saved traceback (356.94 KB, text/plain)
2009-04-14 02:38 UTC, Bruno Wolff III
no flags Details

Description Bruno Wolff III 2009-04-14 02:38:47 UTC
Created attachment 339406 [details]
Saved traceback

Description of problem:
After asking to write the new storage layout to disk I got the attached traceback.

Version-Release number of selected component (if applicable):
livecd-fedora-livecd-testday-20090414-i386.iso

How reproducible:
Seems to happen regularly but I haven't done multiple tests with the testday livecd. I was seeing similar problems with other install/live images.

Steps to Reproduce:
1. I expect that most of the layout info is in the traceback. The only odd aspect when I did this set up was first selecting ext3 for / which was rejected because the livecd was using ext4 and I changed it without backing out of the custom layout page.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Bruno Wolff III 2009-04-14 02:43:59 UTC
I tried it again without having to edit /'s fs type and still saw the same thing.

Comment 2 Bruno Wolff III 2009-04-15 01:26:24 UTC
Wiping the partition info, using the April 14th boot.iso and using the updates kernel parameter to pick up the test day updates.img got me past this issue.
So possibly the partition or raid info was bad (from previous install tries) and causing a problem.
As I mentioned on irc, I did several install tries from the livecd without rebooting since after a failed install attempt I was back at the livecd desktop.
(Which I thought was a nice feature, but was advised one that I shouldn't take advantage of.)

Comment 3 Joel Andres Granados 2009-04-17 13:50:23 UTC

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


Note You need to log in before you can comment on or make changes to this bug.