Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 400311

Summary: unhandled exception occurs on disk formating on HP DL580 G5
Product: Red Hat Enterprise Linux 3 Reporter: stogsdill
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 3.0   
Target Milestone: ---   
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-07-12 01:33:42 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
Trackback (most recent call last) from exception screen none

Description stogsdill 2007-11-26 23:46:15 UTC 
Description of problem:


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


How reproducible:
Easy

Steps to Reproduce:
1. Boot HP DL580 G5 off of CD with ks.cfg file having partiion scheme
2.
3.
  
Actual results:
Displays Exception Occured error message

Expected results:


Additional info:
Comment 1 stogsdill 2007-11-26 23:46:15 UTC 
Created attachment 269381 [details]
Trackback (most recent call last) from exception screen
Comment 2 Chris Lumens 2008-07-12 01:33:42 UTC 
We are no longer producing updated anaconda packages for RHEL3, so sadly there
isn't really anything we can do as far as fixing this bug.  If at all possible,
please try a later release of RHEL (4 if necessary, but 5 preferably) and see if
you continue to experience this problem.  If so, please open a new bug report
with the complete traceback and we'll see what we can do for you.

Thanks for the bug report.