Bug 64188 - trying to update my redhat 7.2 system I recieve the attached message that an unknown status has occured. As a result I can't move on with the update process, it terminates itself clearly and I can reboot the system.
trying to update my redhat 7.2 system I recieve the attached message that an ...
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-04-28 10:42 EDT by dawedawe
Modified: 2008-01-17 12:49 EST (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:48:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description dawedawe 2002-04-28 10:42:12 EDT
Description of Problem:








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








How Reproducible:








Steps to Reproduce:


1. 


2. 


3. 





Actual Results:








Expected Results:








Additional Information:cpu pentiumII 350mhz/tnt2 m64/soundblaster16 value pnp/ motherboard: GA-6BXC  Intel440BX AGPset/ IBM harddisk
Comment 1 Michael Fulbright 2002-04-30 14:51:37 EDT
Transcribing report into proper area, original report is:

"trying to update my redhat 7.2 system I recieve the attached message that an
unknown status has occured. As a result I can't move on with the update process,
it terminates itself clearly and I can reboot the system."
Comment 2 Michael Fulbright 2002-04-30 14:52:15 EDT
Could you please attach the error log?
Comment 3 Michael Fulbright 2002-05-23 12:54:36 EDT
Closing due to inactivity - please reopen if you have additional comments to add
to this bug.
Comment 4 Red Hat Bugzilla 2006-02-21 13:48:47 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.