Bug 134366 - Attempting to edit LVM logical volume during install crashes anaconda
Summary: Attempting to edit LVM logical volume during install crashes anaconda
Status: CLOSED DUPLICATE of bug 132217
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-01 18:20 UTC by Jim Simmons
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 19:06:04 UTC
Target Upstream Version:

Attachments (Terms of Use)
Anaconda dump (52.10 KB, text/plain)
2004-10-01 18:22 UTC, Jim Simmons
no flags Details

Description Jim Simmons 2004-10-01 18:20:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914

Description of problem:
Doing an "Install" (as opposed to an Upgrade) on a system that has
RHEL 3 WS installed using LVM for everything but /boot.  Selected
"Manually partition with Disk Druid", edited the /boot partition, then
selected the "root" logical volume and clicked edit to specify mount
point, filesystem etc.  As soon as you click Edit, anaconda crashes.

See attached anaconda dump.

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

How reproducible:

Steps to Reproduce:
1.Start an Install (doing an NFS install but that shouldn't matter).
2.Select Install instead of Upgrading the existing RHEL 3 WS
configured with LVM.
3.Select the existing "root" logical volume, click Edit.

Actual Results:  Anaconda crashes.

Expected Results:  It should have allowed specifying the mount point,
filesystem type, etc.

Additional info:

Comment 1 Jim Simmons 2004-10-01 18:22:09 UTC
Created attachment 104637 [details]
Anaconda dump

Comment 2 Jeremy Katz 2004-10-01 18:45:27 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:06:04 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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