Bug 49288

Summary: beta2 failed to install to the second HD in text mode.
Product: [Retired] Red Hat Linux Reporter: hjl
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE 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: 2001-07-18 23:58:28 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:
Bug Depends On:    
Bug Blocks: 634001    
Attachments:
Description Flags
traceback none

Description hjl 2001-07-17 18:13:19 UTC 
Description of Problem:

beta2 failed to install to the second HD in text mode.

How Reproducible:

Select text mode and custom install.

Steps to Reproduce:
1. Select text mode 
2. Select custom install.
3.  Use disk druid to install on the second HD

Actual Results:

After exiting from disk druid, anaconda aborted.
Comment 1 hjl 2001-07-17 18:14:44 UTC 
Created attachment 23915 [details]
traceback
Comment 2 hjl 2001-07-17 18:20:45 UTC 
sda6 is the existing swap partition on the first HD. The
GUI install has no probem with it.
Comment 3 Glen Foster 2001-07-17 18:56:32 UTC 
This defect considered MUST-FIX for Fairfax gold-release.
Comment 4 Jeremy Katz 2001-07-18 23:08:00 UTC 
Did you specify a / partition?  From the traceback, it looks almost like the
install didn't have a / partition specified.
Comment 5 hjl 2001-07-18 23:58:24 UTC 
I changed my machine configuration. I cannot reproduce it anymore.
The configuration it failed is

1. sda has RedHat 7.1.
2. sdb is empty.
3. I tried to install beta2 to sdc with swap on sda.

In any case,  anaconda shouldn't crash.
Comment 6 Jeremy Katz 2001-07-22 19:53:40 UTC 
I can't reproduce it at all here.  We've got more sanity checking now so that
cases which could theoretically get you to a condition like you saw should never
happen and if they do, we raise an exception that tells that this is something
which should never happen.  Unfortunately, I'd much rather raise an exception in
these cases because there's a chance that the crash dump could reveal something
about how the problem came about, but in your case, it unfortunately does not.