Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 113280 - Cannot Upgrade ver 8 to 9 or Install ver 9. Keep getting same exception
Cannot Upgrade ver 8 to 9 or Install ver 9. Keep getting same exception
Status: CLOSED DUPLICATE of bug 113279
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
high Severity high
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-01-11 19:59 EST by Peter Aganyo
Modified: 2006-02-21 14:00 EST (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description Peter Aganyo 2004-01-11 19:59:46 EST
Description of problem: Trying to upgrade ver 8 to ver 9. Get 

Tried installing ver 9 (new copy - not upgrade). Get same exception. 

Initial procedures OK upto advanced boot loader configuration. Then 
displays Reading Packages ... , after a while exception occurs.

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

How reproducible: At [Reading Packages .....] stage

Steps to Reproduce:
1. Insert First CD into Drive
2. Restart Computer and Start installation by pressing ENTER
3. Select Locale and other options and click ok to start actual 
Actual results:
Computer displays Reading Packages ..... for a while
The Exception Window appears and gives option to save exception dump.
It is the same error whether upgrading or installing anew.

Expected results:
Actual installation to commence

Additional info:
Same error for whether upgrading or installing shrike anew.
Comment 1 Jeremy Katz 2004-01-13 15:12:58 EST

*** This bug has been marked as a duplicate of 113279 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:00:43 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.