Migrating the Uyuni Proxy to openSUSE Tumbleweed
This page describes how to migrate a Uyuni Proxy host from openSUSE Leap Micro 5.5 to a fresh openSUSE Tumbleweed installation using the proxy administration tool mgrpxy.
|
This guide was tested on Tumbleweed only. There is no known reason it wouldn’t work on other supported bases, but always validate in a test environment before production. |
1. Overview of the Proxy Migration Process
You will:
-
Save proxy configuration from the old system (including Apache/Squid tuning).
-
Reinstall the host with openSUSE Tumbleweed.
-
Re-register the host using the system reactivation key.
-
Install
mgrpxy(and Podman if needed). -
Restore configuration and run
mgrpxy install podmanwith optional tuning files.
2. Requirements and Considerations
-
Keep the same hostname/FQDN and IP when possible so the server and clients interact with the proxy as before.
-
Ensure you have the “system reactivation key” for the existing proxy system (UI: Systems > select the proxy > Details > Reactivation).
-
Ensure SSH/scp access to move configuration archives off and onto the machine.
3. Migration Procedure
3.1. Step 1: Save Proxy Configuration and Tuning Files
Copy the Uyuni proxy configuration directory to a safe location:
scp -r /etc/uyuni <USER>@<HOST>:/some/where/safe/Identify Apache and Squid tuning files currently in use by the legacy proxy services:
systemctl cat uyuni-proxy-httpd.service | grep EXTRA_CONF= | sed 's/.*=-v\([^:]\+\):.*/\1/' systemctl cat uyuni-proxy-squid.service | grep EXTRA_CONF= | sed 's/.*=-v\([^:]\+\):.*/\1/'Copy those tuning files to the same safe location as well.
Typical default paths after you copy them back will be:
Apache tuning:
/etc/uyuni/proxy/apache.confSquid tuning:
/etc/uyuni/proxy/squid.conf
3.2. Step 2: Reinstall the Host with openSUSE Tumbleweed
Reinstall the machine with openSUSE Tumbleweed (server profile recommended).
Set the same hostname/FQDN and IP as before when possible.
3.3. Step 3: Re-register the Host with the Reactivation Key
From the Uyuni Web UI, obtain the system reactivation key for the existing proxy system record (Systems > Details > Reactivation).
Bootstrap/re-register the Tumbleweed host using that reactivation key so it claims the existing system entry.
Use your standard bootstrapping process for Tumbleweed hosts in your environment (for example, the bootstrap script or your configuration management), ensuring the reactivation key is applied.
3.4. Step 4: Install Uyuni Proxy Tools and Podman
Add the Uyuni Stable repository and install tools:
zypper ar https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/images/repo/Uyuni-Proxy-POOL-x86_64-Media1 uyuni-proxy-stable zypper ref zypper in mgrpxy mgrctl mgrpxy-bash-completion mgrctl-bash-completionEnsure Podman is installed (required to run containers):
zypper in podman
3.5. Step 5: Restore Configuration and Install the Proxy
Copy back the saved configuration directory to the new host:
scp -r <USER>@<HOST>:/some/where/safe/uyuni /etc/If you saved Apache/Squid tuning files, place them at the expected default paths or note their locations for parameters in the next command:
# Default paths expected by mgrpxy parameters (adjust/move your files accordingly) # Apache tuning: /etc/uyuni/proxy/apache.conf # Squid tuning: /etc/uyuni/proxy/squid.confRun the proxy installation with Podman. If you do not use tuning files, omit the corresponding parameters:
# With tuning files mgrpxy install podman \ --tuning-httpd /etc/uyuni/proxy/apache.conf \ --tuning-squid /etc/uyuni/proxy/squid.conf # If you have no tuning files, remove the tuning parameters: # mgrpxy install podman
In an upcoming release, if tuning files are placed at the default paths noted above, the explicit parameters will not be required.
3.6. Step 6: Verify the Proxy
Check containers are running:
mgrctl ps # or podman psConfirm the proxy appears healthy in the Uyuni Web UI and that clients using this proxy operate normally.
4. Troubleshooting
-
If Podman was missing, install it and rerun the
mgrpxy installstep. -
Verify the host’s time, hostname, and IP match expectations.
-
If the host did not reattach to the existing system record, confirm you used the correct reactivation key and repeat the bootstrap.