Bug 78226 - Missing file causes installation to abort everytime
Missing file causes installation to abort everytime
Status: CLOSED DUPLICATE of bug 75377
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
8.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-20 08:05 EST by Don Hardaway
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:50:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
anaconda install failure dump (66.25 KB, patch)
2002-11-25 22:39 EST, Need Real Name
no flags Details | Diff
willicat: this is my anaconda-dump, I had the same error... (76.16 KB, text/plain)
2002-12-29 07:04 EST, Sebastian Krieg
no flags Details

  None (edit)
Description Don Hardaway 2002-11-20 08:05:37 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Everytime i try to install rh8.0 on my server it crashes during the
installation. Here is the message generated.

Exception Occurred

An unhandled exception has occurred. This is most likely a bug. Please copy the
full text of this exception or save the crash dump to a floppy then file a
detailed bug report against anaconda at http://bugzilla.redhat.com/bugzilla/

Traceback (most recent call last):
File "/usr/bin/anaconda", line 694, in ?
intf.run(id, dispatch, configFileData)
File "/usr/lib/anaconda/text.py", line
446, in run dispatch.gotoNext()



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


How reproducible:
Always

Steps to Reproduce:
1.load cd1
2.answer all questions about language and format the disk
3.begin the install
	

Actual Results:  aborts

Expected Results:  completes successfully

Additional info:
Comment 1 Michael Fulbright 2002-11-20 10:03:19 EST
Please attach the error dump from the floppy you saved it to.
Comment 2 Don Hardaway 2002-11-20 10:53:38 EST
I did not send one to floppy so if that is needed, I will have to do the install
again to get it.  Meanwhile here is some other info: when i first tried to
install several weeks ago I followed the normal install screens. This last time
I was instructed by you web support people to type in "linux nodma text" at the
prompt. During that install I received the error message I submitted earlier.
From previous attempts where I just followed the install screens it generated an
error message that said this:


The file /mnt/sysimage/var/tmp/Omni-0.7.0-6.i386rpm can not be opened.

It also mentions that it is probably a bug in the install cd--that a file is
missing that it needs.


I will make another trip to campus where the server is and get the floppy dump
and post it.  Meanwhile my server can not be used. If there is anyway that I can
load rh8.0 meanwhile please let me know. I only need it for apache, ssh, and ftp
at this time.
Comment 3 Need Real Name 2002-11-25 22:39:34 EST
Created attachment 86448 [details]
anaconda install failure dump
Comment 4 Don Hardaway 2002-11-26 08:16:38 EST
My last attempt to install rh8.0 somehow worked. I must have checked different
packages to install.  I am not sure which packages I had checked to install the
last 4 times but the error must be associated with a missing file in one of
those choices.
Comment 5 Sebastian Krieg 2002-12-29 07:04:06 EST
Created attachment 88974 [details]
willicat: this is my anaconda-dump, I had the same error...

Hi,
I had he same error during installation in several cases and serveral packages
(graphical/non-graphical mode). I need around 20 trials making a minimal
installation.
Comment 6 Jeremy Katz 2003-01-08 19:32:03 EST

*** This bug has been marked as a duplicate of 75377 ***
Comment 7 Red Hat Bugzilla 2006-02-21 13:50:10 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.