Bug 64720

Summary: Installer exception in anaconda in scanForRaid()
Product: [Retired] Red Hat Linux Reporter: Jess Gehin <gehinjc>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-10 15:48:05 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
dump file written to floppy after installation failure none

Description Jess Gehin 2002-05-10 02:00:33 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0rc1) Gecko/20020417

Description of problem:
Performing an upgrade from 7.2 to 7.3.  Directly after selecting upgrade option
and hitting next an exception in anaconda is reported.

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


How reproducible:
Always

Steps to Reproduce:
1.Boot off of 7.3 cdrom
2.Choose all of the defaults for language, keyboard, mouse
3.Choose "Upgrade" option and hit next
	

Actual Results:  Exception reported with traceback. Output saved to floppy and
inlcuded as an attachment.

Expected Results:  Installation continues

Additional info:

Problem seems to be in the checking for raid systems.  This machine does not
have any (software or hardware) raid partitions or filesystems
Comment 1 Jess Gehin 2002-05-10 02:01:47 UTC 
Created attachment 56867 [details]
dump file written to floppy after installation failure
Comment 2 Jeremy Katz 2002-05-10 22:34:17 UTC 
Can you try using the update disk available at
http://people.redhat.com/~katzj/73raid.img?  If you put that on a separate
floppy and boot with 'linux updates', inserting the disk when prompted, it
should fix the problem.

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