Bug 136422 - kickstart upgrade fails
kickstart upgrade fails
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
3.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-19 17:43 EDT by Abel Lopez
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-19 17:51:28 EDT
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 dump (60.22 KB, text/plain)
2004-10-19 17:45 EDT, Abel Lopez
no flags Details
syslog (29.03 KB, text/plain)
2004-10-19 17:45 EDT, Abel Lopez
no flags Details

  None (edit)
Description Abel Lopez 2004-10-19 17:43:52 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914
Firefox/0.10

Description of problem:
When attempting to upgrade an existing redhat 8.0 system to enterprise
WS 3.0 via kickstart, anaconda dies and provides a traceback.
kickstart fresh install works, only fails when attempting upgrade

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


How reproducible:
Always

Steps to Reproduce:
1. start with a redhat linux 8.0 system
2. make a kickstart profile for upgrade
3. pxeboot will load kernel and search for existing installations,
then fail shortly thereafter
    

Actual Results:  anaconda crash message

Expected Results:  it should have upgraded to enterprise ws 3.0

Additional info:
Comment 1 Abel Lopez 2004-10-19 17:45:03 EDT
Created attachment 105470 [details]
anaconda dump
Comment 2 Abel Lopez 2004-10-19 17:45:27 EDT
Created attachment 105471 [details]
syslog
Comment 3 Jeremy Katz 2004-10-19 17:51:28 EDT
Upgrades from Red Hat Linux to Red Hat Enterprise Linux are not supported.

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