Bug 432427

Summary: Anaconda throws error when trying to re-format existing layout
Product: Red Hat Enterprise Linux 5 Reporter: Jed Laundry <jed.laundry>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5.1   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-12 12:49:23 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:

Description Jed Laundry 2008-02-11 23:24:56 UTC
Description of problem:
When I run up a fresh re-installation on a RHEL 5.1 server, and try to preserve
the existing disk structure while simply reformatting the partitions, Anaconda
brings up a debug window (which I didn't have time to write down, sorry) and I
have to restart the server and start again. I've tried and been able to
reproduce this twice.

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

How reproducible:
The partition structure that we use is four drives in RAID-10, the two virtual
drives being LVM partitions, one volume group, and 5 logical volumes; 4 ext3 and
1 swap.

Steps to Reproduce:
1. Install RHEL 5.1 with the above disk layout (software packages should be
irrelevant, and one LVMed drive should also produce the same result)
2. Try to reinstall RHEL 5.1 by preserving the existing layout and reformatting
the partitions
  
Actual results:
Anaconda crashes with debug window, have to restart server.

Expected results:
Move to boot loader configuration page.

Additional info:
None.

Comment 1 AD 2008-03-05 04:03:18 UTC
Probably related to http://bugs.centos.org/view.php?id=2686

Comment 2 Joel Andres Granados 2008-06-12 12:49:23 UTC
This looks like 224088. and 415871.

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