Bug 442093

Summary: Anaconda traceback when using 20080409.0 install tree
Product: Red Hat Enterprise Linux 5 Reporter: Gary Case <gcase>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.2CC: dwa
Target Milestone: rcKeywords: Regression
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-04-14 19:15:30 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
exception details for anaconda problem
none
Anaconda traceback none

Description Gary Case 2008-04-11 17:33:57 UTC 
Description of problem:
Installation of RHEL5.2 beta from 20080409.0 install tree x86_64 fails with an
anaconda traceback.

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

How reproducible:
Every time 

Steps to Reproduce:
1. Begin RHEL installation
2. Point system to NFS install point, continue using all default choices
3. Exception occurs after partitioning information is entered
  
Actual results:
Install failure

Expected results:
Completed install

Additional info:
I'm attaching the remote capture file for the traceback.
Comment 1 Gary Case 2008-04-11 17:33:57 UTC 
Created attachment 302150 [details]
exception details for anaconda problem
Comment 2 David Aquilina 2008-04-11 18:39:56 UTC 
Created attachment 302155 [details]
Anaconda traceback

I believe I ran into the same traceback... here's my debug log.
Comment 3 RHEL Program Management 2008-04-11 18:44:30 UTC 
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.
Comment 4 Brock Organ 2008-04-14 19:15:30 UTC 

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