Description of problem: rhn-upgrade docs needs to be updated to mention that pre 3.6 satellites needs to upgraded to 3.6 level before upgrading to 5.2 as per my conversation with michael I was told that sat 3.6 is the oldest version supported in 5.2.0 upgrade. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. install the rhn-upgrade-5.2.0-28.el4 2. cat rhn-satellite-5-upgrade-scenario-1a.txt and rhn-satellite-5-upgrade-scenario-1b.txt 3. schema upgrade has steps starting at schema version 2.6 Actual results: schema upgrade has steps starting at schema version 2.6 Expected results: if the oldest satellite level you can upgrade to 5.2 is 3.6 then these steps up until 3.6 schema upgrade needs to be deleted from the doc . Additional info:
here is the irc log Feb 26 10:20:49 michael sat 3.2 contains oracle 9.2.0.3; the older oracle which can be upgraded to 10g is 9.2.0.4....
Based on Comment #3 From Michael Mráka, this makes sense now, so approved.
satellite.git SATELLITE-5.3: 528fe5d94777ffe436cd17ec3ca5c74464a46c3b Upgrade documentation no longer lists the particular steps for schema upgrade for every single schema version. This job is being done automatically now by spacewalk-schema-upgrade script (as mentioned in documentation). With 5.3.0, we support upgrades from schemas ver. 3.1.5 and newer (which is mentioned in README document). About the embedded database upgrade: I made a note in README document telling that to be able to upgrade embedded database to 10g, customer needs to have at least version 9.2.0.4 of 9i database (which came with Satellite 3.6). If customer is running 9i ver. 9.2.0.3 or older, he needs to upgrade his Satellite to any version between 3.6 and 5.1 first (also mentioned in README).
rhn-upgrade-5.3.0.7-1
Verified
/etc/sysconfig/rhn/satellite-upgrade/README contains text from #5 verified in stage on xen5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1235.html