Proxy Migration
Upgrading from SUSE Manager Proxy 3.2 with the latest service pack (SP) to version 4 can be automated, but requires some preparation steps.
Preliminary Considerations
The recommended order for migrations is to first migrate the SUSE Manager server and then the proxies.
Using SUSE Manager Proxy 3.2 with SUSE Manager 4
SUSE Manager Proxy 3.2 is compatible with SUSE Manager Server 4. After the server has been migrated to version 4, proxies can be automatically upgraded from the SUSE Manager server using YaST autoinstallation. |
Migrating SUSE Manager Proxy 3.2 only works for proxies that have been registered as traditional clients. Proxies that are Salt minions cannot be migrated to the new version this way.
Upgrading SUSE Manager Proxy In-place
-
Create an autoinstallation distribution based on SLE 15 SP1. Use the SLE Installer media. This is required because SUSE Manager Proxy 4 is a product of the SUSE Linux Enterprise 15.1 product family. As the
Base Channel
selectSLE-Product-SUSE-Manager-Proxy-4.0-Pool for x86_64
and as theInstaller Generation
selectSUSE Linux Enterprise 15
.For information on creating an autoinstallation distribution, see xref:#ref.webui.systems.autoinst.distribution (
). -
Create an autoinstallation profile. xref:#proxy-migration-inplace-profile includes a template autoinstallation profile for your use. In this example, the label
proxy4
is used for both the autoinstallation distribution and for the autoinstallation profile. Replace the labelproxy4
with the one you use for your autoinstallation profile.
Autoinstallation Profile
Use this autoinstallation profile as an example.
<?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <add-on> <add_on_products config:type="list"> <listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>http://$redhat_management_server/ks/dist/child/sle-product-suse-manager-proxy-4.0-updates-x86_64/proxy4</media_url> <name>sle-product-suse-manager-proxy-4.0-updates-x86_64</name> <product>SUSE Manager Proxy 4.0</product> <product_dir>/</product_dir> </listentry> <listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>http://$redhat_management_server/ks/dist/child/sle-module-basesystem15-sp1-pool-x86_64-proxy-4.0/proxy4</media_url> <name>sle-module-basesystem15-sp1-pool-x86_64-proxy-4.0</name> <product>SUSE Manager Proxy 4.0</product> <product_dir>/</product_dir> </listentry> <listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>http://$redhat_management_server/ks/dist/child/sle-module-basesystem15-sp1-updates-x86_64-proxy-4.0/proxy4</media_url> <name>sle-module-basesystem15-sp1-updates-x86_64-proxy-4.0</name> <product>SUSE Manager Proxy 4.0</product> <product_dir>/</product_dir> </listentry> <listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>http://$redhat_management_server/ks/dist/child/sle-module-server-applications15-sp1-pool-x86_64-proxy-4.0/proxy4</media_url> <name>sle-module-server-applications15-sp1-pool-x86_64-proxy-4.0</name> <product>SUSE Manager Proxy 4.0</product> <product_dir>/</product_dir> </listentry> <listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>http://$redhat_management_server/ks/dist/child/sle-module-server-applications15-sp1-updates-x86_64-proxy-4.0/proxy4</media_url> <name>sle-module-server-applications15-sp1-updates-x86_64-proxy-4.0</name> <product>SUSE Manager Proxy 4.0</product> <product_dir>/</product_dir> </listentry> <listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>http://$redhat_management_server/ks/dist/child/sle-module-suse-manager-proxy-4.0-pool-x86_64/proxy4</media_url> <name>sle-module-suse-manager-proxy-4.0-pool-x86_64</name> <product>SUSE Manager Proxy 4.0</product> <product_dir>/</product_dir> </listentry> <listentry> <ask_on_error config:type="boolean">true</ask_on_error> <media_url>http://$redhat_management_server/ks/dist/child/sle-module-suse-manager-proxy-4.0-updates-x86_64/proxy4</media_url> <name>sle-module-suse-manager-proxy-4.0-updates-x86_64</name> <product>SUSE Manager Proxy 4.0</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> <general> $SNIPPET('spacewalk/sles_no_signature_checks') <mode><confirm config:type="boolean">false</confirm></mode> </general> <upgrade> <only_installed_packages config:type="boolean">false</only_installed_packages> <stop_on_solver_conflict config:type="boolean">true</stop_on_solver_conflict> </upgrade> <backup> <sysconfig config:type="boolean">true</sysconfig> <modified config:type="boolean">true</modified> <remove_old config:type="boolean">false</remove_old> </backup> <networking> <keep_install_network config:type="boolean">true</keep_install_network> <start_immediately config:type="boolean">true</start_immediately> </networking> <software> <image/> <install_recommended config:type="boolean">true</install_recommended> <instsource/> <patterns config:type="list"> <pattern>suma_proxy</pattern> </patterns> <products config:type="list"> <listentry>SUSE-Manager-Proxy</listentry> </products> </software> <scripts> <chroot-scripts config:type="list"> <script> <filename>cleanup.sh</filename> <chrooted config:type="boolean">true</chrooted> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh sysconf_addword /etc/sysconfig/apache2 APACHE_MODULES wsgi if [ -e /etc/rhn/rhn.conf.rpmsave ]; then cp /etc/rhn/rhn.conf.rpmsave /etc/rhn/rhn.conf fi zypper rr --all ]]> </source> </script> </chroot-scripts> </scripts> </profile>
Before proceeding make sure all the channels referenced in the autoinstallation profile are available and fully synchronized.
Running the In-place Upgrade
-
In the SUSE Manager Web UI, upload the edited autoinstallation profile to your SUSE Manager server (
). -
In the
Kernel Options
field, enter this value:autoupgrade=1 Y2DEBUG=1
The debug setting is not required but can help with investigating future problems you might encounter. The
autoupgrade
parameter, however, is mandatory. -
Select the proxy from the system list in SUSE Manager, click the
Provisioning
tab, and select the profile you created earlier. -
Click Schedule Autoinstallation and Finish. The system will download the needed files, change the bootloader entries, reboot, and start the upgrade.
Cleaning Up After the In-place Upgrade
After the proxy has completed the automatic upgrade process, it still will have the old channels from SUSE Manager assigned.
If the server reports that there are updates available for the proxy, do not apply them. |
Select the proxy from the system list and click Base Channel
, select SLE-Product-SUSE-Manager-Proxy-4.0-Pool for x86_64
and as Child Channels
all the recommended channels:

All the clients connected with the previous SUSE Manager Proxy can access the SUSE Manager Server again and the proxy itself can be managed by the server as before.