Proxy - Upgrade Procedure
Before you perform any proxy update, schedule a maintenance window. The clients registered to SUSE Manager through the proxy will not be able to connect to SUSE Manager while the update is in progress. For more information about maintenance windows, see Maintenance Windows.
As a preparation step, add the openSUSE Leap 15.3 channels to the server.
At the command prompt on the SUSE Manager Server, as root, use the
spacewalk-common-channelscommand to add the appropriate channels:
spacewalk-common-channels opensuse_leap15_2 \ opensuse_leap15_2-non-oss \ opensuse_leap15_2-non-oss-updates \ opensuse_leap15_2-updates \ opensuse_leap15_2-uyuni-client \ uyuni-proxy-stable-leap-152
Fully synchronize all channels with
spacewalk-repo-sync. In case of already defined repository URLs, continue with Troubleshooting Duplicate Repository URLs.
If you add two or more repositories with the same URL (client tools for openSUSE Leap 15.0, 15.1, and 15.2) in SUSE Manager with
spacewalk-common-channels, an error like this is shown:
ERROR: opensuse_leap15_2-uyuni-client-x86_64: redstone.xmlrpc.XmlRpcFault: There's already a defined repository with given url, please reuse it
Work around with assigning the 15.1 repository to the 15.2 channel:
In the SUSE Manager Server Web UI, navigate toand click the
Uyuni Client Tools for openSUSE Leap 15.2 (x86_64)channel name.
In the upper right corner, click Manage Channel.
Navigate to the
Repositoriestab, and select
External - Uyuni Client Tools for openSUSE Leap 15.1 (x86_64).
Click Update Repositories.
Navigate tosubtab, and click Sync Now.
Do the same with
Uyuni Proxy Stable for openSUSE Leap 15.2 (x86_64)and
External - Uyuni Proxy Stable for openSUSE Leap 15.1 (x86_64).
openSUSE Leap 15.2 (x86_64) channel to see the child channels populated with packages.
To upgrade a proxy you first stop the proxy service, then you replace the software repositories and update the software, and finally you restart the proxy service.
In the SUSE Manager Server Web UI, navigate to proxy system’s details page, click the
Click Generate New Key to generate a reactivation key.
On the SUSE Manager Proxy, stop the proxy service:
In the SUSE Manager Server Web UI, navigate toand click the name of the proxy.
Click, and as the base channel select the openSUSE Leap 15.3 channel that is listed in the
Child Channelspane, select the 15.3 child channels.
Click Next, and
Confirm Software Channel Changewith Confirm.
Click, and select all the packages to be updated on the proxy, and then apply the selection.
Re-register with the reactivation key using the
rhnreg_kscommand-line utility. The system is re-registered with the same ID, history, and groups.
On the SUSE Manager Proxy, start the proxy service:
If you need to update many proxies, you can create an action chain of this command sequence on the SUSE Manager Server. You can use the action chain to perform updates on multiple proxies at the same time.