Bug 399471 - [EMC 4.7 bug] Get unexpected exception when updating from RHEL 4 U4 to RHEL 4.6
[EMC 4.7 bug] Get unexpected exception when updating from RHEL 4 U4 to RHEL 4.6
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Depends On:
Blocks: 241692
  Show dependency treegraph
Reported: 2007-11-26 09:25 EST by Wayne Berthiaume
Modified: 2008-01-28 10:36 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-28 10:36:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
ncurses exception (110.83 KB, image/pjpeg)
2007-11-26 09:25 EST, Wayne Berthiaume
no flags Details
GUI error (100.33 KB, image/pjpeg)
2007-11-26 09:28 EST, Wayne Berthiaume
no flags Details

  None (edit)
Description Wayne Berthiaume 2007-11-26 09:25:46 EST
Description of problem:
Get unexpected exception when updating from RHEL 4 U4 to RHEL 4.6 with either 
ncurses or GUI based installation. See attached screenshots.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Wayne Berthiaume 2007-11-26 09:25:46 EST
Created attachment 268941 [details]
ncurses exception
Comment 2 Wayne Berthiaume 2007-11-26 09:28:23 EST
Created attachment 268951 [details]
GUI error
Comment 3 Wayne Berthiaume 2007-11-26 09:29:20 EST
These errors occur after determining the partitioning.
Comment 4 Alexander Todorov 2007-11-28 11:22:41 EST
Wayne, what is your partitioning table? 

Does the error happen when upgrading RHEL4-U4->U5->U6 ?

The "official" way to upgrade between minor releases (e.g. U?) is to upgrade to
the next version, not skip entire release. Try upgrading to RHEL4-U5 first, and
then to RHEL4-U6 and let us know.
Comment 5 Alexander Todorov 2007-11-28 11:24:03 EST
I forgot to say that fro upgrades between minor releases it's reccomended to use
yum (RHEL5) or up2date (RHEL4), either with RHN or a local repository.
Comment 6 Alexander Todorov 2008-01-10 05:19:25 EST
Please reply to comment #4 (#5). If I don't get an update I will need to close
this issue with INSUFFICIENT_DATA 
Comment 7 Wayne Berthiaume 2008-01-10 09:44:44 EST
Hi Alex.

    I've been using the default partitioning on both RHEL 4 U4 and RHEL 4.6. 
The update was being performed via booting CD 1.

Comment 8 Alexander Todorov 2008-01-11 02:59:51 EST
does the issue happen when upgrading RHEL4-U4->U5->U6 using u2pdate (RHN or
local directory) ?
Comment 9 Wayne Berthiaume 2008-01-15 09:22:15 EST
Unfortunately, I had only the one server I was updating in this fashion and 
have since performed a clean install on it. 
Comment 10 Andrius Benokraitis 2008-01-16 23:06:35 EST
Wayne, so... this isn't too good then for reproducing the issue. Would you be
opposed to closing this until you experience it again?
Comment 12 Wayne Berthiaume 2008-01-28 10:36:32 EST
In light of the difficulties to reproduce it I have no problem with closing 

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