Bug 492248

The current KB article (http://kbase.redhat.com/faq/docs/DOC-10806) remains valid for some instances. 
We may want to rename (or rather copy current content to new article) it to "How do I upgrade my Satellite Proxy to the latest version using reprovision?"
On top of this article we should state:

You will need to follow this instructions if you:
 * have Satellite 5.0 or older
 * you upgrade underlaying OS (e.g you are upgrading from RHEL 4AS to RHEL
   5Server).
For other scenarion exists less painful way. See "How do I upgrade my Satellite Proxy to latest version".

In this article, can be deleted few parts which are no longer necessery, due
end of life of given version:
In section Preparation -> 1. ** Otherwise
  all proxy should be graeater then 3.6
** Additionally if version 1.1.1 is present:
  that can be deleted as well
In chapter:
Restoring SSL build directory and generating a tar archive
Upgrading from RHN Proxy Server version 1.1.1
	- can be deleted
Upgrading from RHN Proxy Server version 3.2.0
	- can be deleted
Upgrading from RHN Proxy Server version 3.2.2
	- can be deleted



KB article "How do I upgrade my Satellite Proxy to latest version" will have
just this content:

There is three possible way of upgrading Satellite Proxy:
 * upgrade using reprovision machine - use this method if you have Satellite
   5.0 or older or you are upgrading uderlaying OS.  See <link to article>
 * upgrade using WebUI installer - this process will remove your Satellite
   Proxy packages and install new packages. No need to reprovisioning. See <link to article>
 * upgrade using Command Line Installer - this is available from Satellite 5.3
   or Satellite Proxy if your Satellite Proxy is connected directly to rhn.redhat.com
   See <link to article>

KB article "How do I upgrade my Satellite Proxy to latest version using
Command Line Installer"

1. Preparation
 Stop Satellite Proxy:
   For Satellite Proxy 5.2 and older:
     # /sbin/service rhn-proxy stop
   For Satellite Proxy 5.3 and newer:
     # /usr/sbin/rhn-proxy stop

 Fully backup you Satellite Proxy

2. Upgrade
 Make sure you are subscribed RHN Tools channel.
 Install package "spacewalk-proxy-installer"
 Run program "/usr/sbin/configure-proxy.sh"
 Answer on question "Proxy version to activate" with proxy version you want
upgrade to and answer all the remaining questions.
 Make sure your packages are updated, by running
   yum upgrade
 on RHEL 5Server or
   up2date -u
 on RHEL 4AS
 You may want to restore your SSL certificates for Apache and Jabberd either
from Configuration channel or from your backup.

3. Start Satellite Proxy
   For Satellite Proxy 5.2 and older:
     # /sbin/service rhn-proxy start
   For Satellite Proxy 5.3 and newer:
     # /usr/sbin/rhn-proxy start


KB article "How do I upgrade my Satellite Proxy to latest version using
WebUI installer"

1. <copy Preparation chapter from original KB article>

2. Deactivate the proxy through the RHN/Satellite web interface. Click on System->Details->Proxy and finally 'Deactivate Proxy'

3. run "rhn_check" on Satellite proxy

4. Activate new version of Satellite Proxy proxy through the RHN/Satellite web interface. Click on System->Details->Proxy->Activate Proxy
   Refer to the Proxy Installation Guide<link> for instructions. 
   You may get asked during the process that Proxy has conflicting packages
and that they will be removed during the process. That is normal and you
should click OK button.

5. After Satellite Proxy is installed you may want to restore your Apache and
Jabberd SSL certificates from backup of from configuration channel.

The ball is on QA side. I'm moving this to ON_QA although the main work (write tests) should be done yet.

The test cases have been made, but they are in Testify rather than Testopia. I
am calling this done, with the condition that they be reproduced in Testopia
ASAP.

Release Pending

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