diff --git a/.changelog b/.changelog index 691f9a73f02..7fd831bf7fc 100644 --- a/.changelog +++ b/.changelog @@ -6,6 +6,7 @@ # Last packaged: 2020-07-02 +- New section Upgrade Uyuni Proxy in Upgrade Guide - New section Upgrade Uyuni Server in Upgrade Guide - Add GPG information about Oracle clients to SUMA (bsc#1173520) - Add hostname admonition to public cloud sections (bsc#1173621) diff --git a/modules/upgrade/nav-upgrade-guide.adoc b/modules/upgrade/nav-upgrade-guide.adoc index 7f2dec70f76..f6b6400d872 100644 --- a/modules/upgrade/nav-upgrade-guide.adoc +++ b/modules/upgrade/nav-upgrade-guide.adoc @@ -22,8 +22,14 @@ ifeval::[{uyuni-content} == true] *** xref:server-major-upgrade-uyuni.adoc[Server - Major Upgrade] endif::[] ** xref:proxy-intro.adoc[Upgrade the Proxy] +ifeval::[{uyuni-content} == true] +// *** xref:proxy-autoyast-uyuni.adoc[Proxy - Upgrade with AutoYaST] +*** xref:proxy-uyuni.adoc[Proxy - Upgrade Procedure] +endif::[] +ifeval::[{suma-content} == true] *** xref:proxy-x.adoc[Proxy - X Upgrade] *** xref:proxy-y-z.adoc[Proxy - Y or Z Upgrade] +endif::[] ** xref:client-intro.adoc[Upgrade the Clients] *** xref:client-x.adoc[Client - X Upgrade] ** xref:db-intro.adoc[Upgrade the Database] diff --git a/modules/upgrade/pages/proxy-autoyast-uyuni.adoc b/modules/upgrade/pages/proxy-autoyast-uyuni.adoc new file mode 100644 index 00000000000..d60e6623782 --- /dev/null +++ b/modules/upgrade/pages/proxy-autoyast-uyuni.adoc @@ -0,0 +1,142 @@ +[[proxy-uyuni-ay]] += Proxy - Upgrade with AutoYaST + + +{productname} Proxy can be upgraded from one major version to the next. +The upgrade process is automated, but you will need to do some preparation steps before you can upgrade. + +You will need to complete the {productname} Server Upgrade before you start. + +The old system must be running {productname} Proxy with all the latest updates applied. +Before you start, ensure that the system is up to date and all updates have been installed successfully. + + + +== Prepare to Upgrade + +Before you can update your proxy, you will need an autoinstallation distribution, and an autoinstallation profile. +The distribution must be based on openSUSE Leap{nbsp}{opensuse-version}. + +.Procedure: Preparing Installation Media +. On the {productname} Server, create a local directory for the openSUSE Leap{nbsp}{opensuse-version} installation media: ++ +---- +mkdir -p /srv/images/opensuse152 +---- +. Download an ISO image with the installation sources, and mount the ISO image on your server: ++ +---- +mount -o loop DVD1.iso /mnt/ +---- +. Copy everything from the mounted ISO to your local file system: ++ +---- +cp -r /mnt/* /srv/images/opensuse152 +---- +. When the copy is complete, unmount the ISO image: ++ +---- +umount /mnt +---- + + +.Procedure: Adding Software Channels at the Command Prompt +. At the command prompt on the {productname} Server, as root, use the [command]``spacewalk-common-channels`` command 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 [command]``spacewalk-repo-sync``. + +//// +Add 15.2 channels to the server with spacewalk-common-channels, sync Leap 15.2 channels, change the proxy to use 15.2 channels instead of 15.1 channels, apply the change then update everything" should work +//// + + + +.Procedure: Creating an Autoinstallation Distribution +. In the {productname} {webui}, navigate to menu:Systems[Autoinstallation > Distributions] and click btn:[Create Distribution]. +. In the [guimenu]``Create Autoinstallable Distribution`` section, use these parameters: +* In the [guimenu]``Distribution Label`` section, type a unique name for the distribution. +Use only letters, numbers, hyphens, periods, and underscores, and ensure the name is longer than four characters. +For example, ``proxy_152-x86_64``. +* In the [guimenu]``Tree Path`` field, type an absolute path to the installation source. +For example, [path]``/srv/images/opensuse152``. +* In the [guimenu]``Base Channel`` field, select [systemitem]``openSUSE Leap 15.2 (x86_64)``. +* In the [guimenu]``Installer Generation`` field, select [systemitem]``SUSE Linux``. +* In the [guimenu]``Kernel Options`` field, type any options to be passed to the kernel when booting for the installation. +The [option]``install=`` parameter and the [option]``self_update=0 pt.options=self_update`` parameter are added by default. +* In the [guimenu]``Post Kernel Options`` section, type any options to be passed to the kernel when booting the installed system for the first time. +. Click btn:[Create Autoinstallable Distribution] to save. + + +When you have created an autoinstallable distribution, you can edit it by navigating to menu:Systems[Autoinstallation > Distributions] and selecting the distribution you want to edit. + + + +== Create an Autoinstallation Profile + +Autoinstallation profiles contain all the installation and configuration data needed to install a system. +They can also contain scripts to be executed after the installation is complete. +For example scripts that you can use as a starting point, see https://github.com/SUSE/manager-build-profiles/tree/master/AutoYaST. + + + +.Procedure: Creating an Autoinstallation Profile +. In the {productname} {webui}, navigate to menu:Systems[Autoinstallation > Profiles] and upload your autoinstallation profile script. +For example scripts that you can use as a starting point, see https://github.com/SUSE/manager-build-profiles/tree/master/AutoYaST. +. In the ``Kernel Options`` field, type ``autoupgrade=1``. +Optionally, you can also include the ``Y2DEBUG=1`` option. +The debug setting is not required but can help with investigating any future problems you might encounter. +. Paste the autoinstallation profile or use the file upload field. +. Click btn:[Create] to save. +. When the uploaded profile requires variables to be set, navigate to menu:Systems[Autoinstallation > Profiles], select the profile to edit, and navigate to the [guimenu]``Variables`` tab. +Specify the required variables, using this format: ++ +---- += +---- + +[NOTE] +==== +For proxies that were registered using Salt, use the ``spacewalk/minion_script`` snippet to register the proxy again after upgrade has completed. +==== + + + +== Upgrade + +Before you begin, check that all the channels referenced in the autoinstallation profile are available and fully synchronized. + + + +.Procedure: Upgrading +. On the {productname} Server {webui}, navigate to menu:Systems[System List], select the proxy, navigate to the [guimenu]``Provisioning`` tab, and select the autoinstallation profile you uploaded. +. Click btn:[Schedule Autoinstallation and Finish]. +The system will download the required files, change the bootloader entries, reboot, and start the upgrade. + + + +== Clean Up + +When the {productname} Proxy has finished upgrading, it shows the originally assigned channels. +Cleaning up after the migration ensures the correct channels are shown. + + +[WARNING] +==== +If the server reports that there are updates available for the proxy, do not apply them before completing the cleanup. +==== + + + +.Procedure: Cleaning Up +. On the {productname} Server {webui}, navigate to the [guimenu]``System List``, select the proxy, and navigate to the menu:Software[Software Channels] subtab. +. Clear the old channels. +. In the [guimenu]``Base Channel`` field, select `openSUSE Leap 15.1 (x86_64)``. +. In the [guimenu]``Child Channels`` field, select all the recommended channels. diff --git a/modules/upgrade/pages/proxy-intro.adoc b/modules/upgrade/pages/proxy-intro.adoc index f4b1e0c8f9d..f6beaa1cd06 100644 --- a/modules/upgrade/pages/proxy-intro.adoc +++ b/modules/upgrade/pages/proxy-intro.adoc @@ -2,14 +2,16 @@ = Upgrade the Proxy {productname} Proxies are managed in the same way as clients. +ifeval::[{suma-content} == true] Maintenance updates (MU) can be installed on a {productname} Proxy in the same way as other clients. MU updates require a restart of the proxy service. +endif::[] Before you perform any proxy update, schedule a maintenance window. The clients registered to {productname} through the proxy will not be able to connect to {productname} while the update is in progress. For more information about maintenance windows, see xref:administration:maintenance-window.adoc[]. - +ifeval::[{suma-content} == true] {productname} uses an [literal]``X.Y.Z`` versioning schema. To determine which upgrade procedure you need, look at which part of the version number is changing. @@ -30,3 +32,4 @@ Upgrading within the same minor version. This is often referred to as a maintenance update. For example, upgrading from 4.0.0 to 4.0.2. See xref:upgrade:proxy-y-z.adoc[]. +endif::[] diff --git a/modules/upgrade/pages/proxy-uyuni.adoc b/modules/upgrade/pages/proxy-uyuni.adoc new file mode 100644 index 00000000000..9aa26452e9e --- /dev/null +++ b/modules/upgrade/pages/proxy-uyuni.adoc @@ -0,0 +1,101 @@ +[[proxy-uyuni-upgrade]] += Proxy - Upgrade Procedure + +Before you perform any proxy update, schedule a maintenance window. +The clients registered to {productname} through the proxy will not be able to connect to {productname} while the update is in progress. +For more information about maintenance windows, see xref:administration:maintenance-window.adoc[]. + + + +== Preparation + +As a preparation step, add the openSUSE Leap {opensuse-version} channels to the server. + +.Procedure: Adding Software Channels at the Command Prompt +. At the command prompt on the {productname} Server, as root, use the [command]``spacewalk-common-channels`` command 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 [command]``spacewalk-repo-sync``. +In case of already defined repository URLs, continue with <>. + + + +[[uyuni-202007-channeldupes]] +== Uyuni 2020.07: Troubleshooting with Duplicated Repository URLs + +// https://github.com/SUSE/spacewalk/issues/12008 + +If you want to add two or more repositories with the same URL (client tools for openSUSE Leap 15.0, 15.1, and 15.2) in {productname} 2020.07 with [command]``spacewalk-common-channels``, you will see an error such as: + +---- +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: + +.Procedure: Assigning 15.1 Repositories to the 15.2 Channel: + +. In the {productname} Server {webui}, navigate to menu:Software[Manage > Channels] and click the [systemitem]`` Uyuni Client Tools for openSUSE Leap 15.2 (x86_64)`` channel name. + +. In the upper right corner, click btn:[Manage Channel]. + +. Click the [guimenu]``Repositories`` tab, and select [systemitem]``External - Uyuni Client Tools for openSUSE Leap 15.1 (x86_64)`` + +. Click btn:[Update Repositories]. + +. Navigate to menu:Repositories[Sync] subtab, and click btn:[Sync Now]. + +. Do the same with [systemitem]``Uyuni Proxy Stable for openSUSE Leap 15.2 (x86_64)`` and [systemitem]``External - Uyuni Proxy Stable for openSUSE Leap 15.1 (x86_64)``. + +If you unfold the [systemitem]``openSUSE Leap 15.2 (x86_64)``, you will see all child channels propulated with packages. + + + +== Upgrade the Proxy + +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. + + + +.Procedure: Updating the {productname} Proxy + +. In the {productname} Server {webui}, navigate to proxy system's details page, click the [guimenu]``Reactivation`` subtab. + +. Click btn:[Generate New Key] to generate a reactivation key. ++ +//// +With a system profile specific activation key, this system can be re-registered using the 'rhnreg_ks' command-line utility. The system will be re-registered with the same id, history, groups, and channels (unless the system's base channel changes). +Key: re-1-1008b9843d44dac77f0a856f207cc2c6 +//// + +. On the {productname} Proxy, stop the proxy service: ++ +---- +spacewalk-proxy stop +---- + +. In the {productname} Server {webui}, navigate to menu:Systems[Proxy] and click the name of the proxy. +. Click menu:Software[Software Channels], and as the base channel select the openSUSE Leap {opensuse-version} channel that is listed in the [systemitem]``Customs Channels`` list. +. In the [guimenu]``Child Channels`` pane, select the {opensuse-version} child channels. +. Click btn:[Next], and [guimenu]``Confirm Software Channel Change`` with btn:[Confirm]. +. Click menu:Software[Packages > Upgrade], and select all the packages to be updated on the proxy, and then apply the selection. +. Re-register with the reactivation key using the [command]``rhnreg_ks`` command-line utility. +The system will be re-registered with the same id, history, and groups. ++ +// and channels (unless the system's base channel changes). +. On the {productname} Proxy, start the proxy service: ++ +---- +spacewalk-proxy start +---- + +If you need to update many proxies, you can create an action chain of this command sequence on the {productname} Server. +You can use the action chain to perform updates on multiple proxies at the same time.