Upgrading orcharhino 7.1 from EL8 to EL9

You can upgrade orcharhino 7.1 on EL8 to orcharhino 7.1 on EL9. This guide describes how you can upgrade the base OS of orcharhino Server and orcharhino Proxy Servers.

The Leapp upgrade requires multiple reboots and takes time depending on your environment. During the Leapp upgrade, orcharhino services are unavailable.

Ensure that you carefully read all of the instructions, warnings, and recommendations presented in this guide and Upgrading orcharhino from EL8 to EL9 in the ATIX Service Portal. ATIX AG does not offer support for recovery from a failed upgrade if you did not follow the upgrade guide.

ATIX AG does not support using third party repositories on your orcharhino Server or orcharhino Proxy Servers. Resolving package conflicts or other issues due to third party or custom repositories is not part of your orcharhino support subscription. Please contact us if you have any questions.

EL9 does not support SSL certificates that rely on SHA-1 as signature algorithm. If your orcharhino Server or any orcharhino Proxy Server relies on external services that use SSL certificates that rely on SHA-1 as signature algorithm, you have to replace those certificates first. For more information, see RHEL 9 Release Notes.

Leapp upgrade paths

You can run orcharhino 7.1 on AlmaLinux 8, Oracle Linux 8, Red Hat Enterprise Linux 8, and Rocky Linux 8. From EL8, orcharhino supports the following Leapp upgrade paths:

  • AlmaLinux 8 > AlmaLinux 9

  • Oracle Linux 8 > Oracle Linux 9

  • Red Hat Enterprise Linux 8 > Red Hat Enterprise Linux 9

  • Rocky Linux 8 > Rocky Linux 9

Upgrading orcharhino Server from EL8 to EL9

You can upgrade orcharhino Server 7.1 from EL8 to EL9.

Prerequisites

  • Ensure that your orcharhino Server runs orcharhino 7.1.

  • Ensure that all your orcharhino Proxy Servers run orcharhino 7.1.

  • If you use custom repositories, please contact us on how to migrate them from EL8 to EL9. Note that this is not supported.

Preparing Leapp on EL8

Procedure

  1. Backup your orcharhino Server:

    ATIX AG recommends running orcharhino as a virtual server and performing a system snapshot at this point. For more information, see Backing up orcharhino.

  2. Update all packages on your orcharhino Server:

    $ dnf upgrade

  3. Install Leapp prerequisites on your orcharhino Server:

    $ dnf install pciutils policycoreutils-python-utils python3 python3-requests python3-setuptools systemd-container

  4. Configure your orcharhino Server:

    $ orcharhino-installer

  5. Reindex your database on orcharhino Server:

    $ runuser -u postgres -- reindexdb -a

    For more information, see Leapp Upgrade fails due to error when reindexing the database in the ATIX Service Portal.

  6. Ensure that /boot provides enough free disk space:

    $ df -h /boot

    For more information, see Deleting old Kernels before the Leapp Upgrade to EL9 in the ATIX Service Portal.

  7. Reboot your orcharhino Server:

    $ reboot

  8. Install Leapp on your orcharhino Server:

    $ dnf install --disablerepo=* --enablerepo=ATIX_orcharhino_Server_EL8_orcharhino_7_1 leapp leapp-repository

Enabling EL9 repositories

Procedure

  1. Enable the required EL9 repositories on your orcharhino Server:

    $ orcharhino-maintain advanced procedure run repositories-setup --version 7.1 --distro-version 9 --distro-name My_Target_OS

    Ensure that you set the target OS according to your Leapp upgrade path:

    • On AlmaLinux 8: almalinux

    • On Oracle Linux 8: oracle

    • On Red Hat Enterprise Linux 8: redhat

    • On Rocky Linux 8: rocky

  2. Switch the or_maintain repository on your orcharhino Server to EL9:

    $ sed -i 's|^baseurl.*$|baseurl = URL_for_or_maintain_for_EL9|g' /etc/yum.repos.d/or_maintain_x86_64.repo

    You can find the URL in Upgrading orcharhino from EL8 to EL9 in the ATIX Service Portal.

  3. On Oracle Linux 8 only: Switch the orcharhino Client for Oracle Linux on your orcharhino Server to EL9:

    $ sed -i 's|^baseurl.*$|baseurl = URL_for_orcharhino_Client_for_Oracle_Linux_9|g' /etc/yum.repos.d/or_oracle_client.repo

    You can find the URL in Upgrading orcharhino from EL8 to EL9 in the ATIX Service Portal.

Running Leapp

Procedure

  1. Set the ENABLE_REPO_LIST environment variable on your orcharhino Server:

    $ export ENABLE_REPO_LIST="$(LANG=C subscription-manager repos --list-enabled | grep '^Repo ID:' | awk '{print $3}' | sed 's/^/--enablerepo=/g' | tr '\n' ' ' | xargs)"

  2. On Oracle Linux 8 only: Extend the ENABLE_REPO_LIST environment variable:

    $ export ENABLE_REPO_LIST="$ENABLE_REPO_LIST --enablerepo=orcharhino_Oracle_9_Client"

  3. Extend the ENABLE_REPO_LIST environment variable:

    $ export ENABLE_REPO_LIST="$ENABLE_REPO_LIST --enablerepo=or_maintain_x86_64"

  4. Perform Leapp pre-upgrade checks:

    $ leapp preupgrade $ENABLE_REPO_LIST

    The Leapp pre-upgrade check reports inhibitors that prevent the Leapp upgrade on orcharhino Server. Examine the report in the /var/log/leapp/leapp-report.txt file and have a look at the most common remediation instructions in Leapp Preupgrade Reports. If you encounter any additional issues, please have a look at Upgrading orcharhino from EL8 to EL9 or contact the orcharhino support team.

  5. After resolving all Leapp upgrade inhibitors, rerun the Leapp pre-upgrade check:

    $ leapp preupgrade $ENABLE_REPO_LIST

    If Leapp reports issues, please contact us.

  6. On Oracle Linux 8 only: Ensure that your orcharhino Server does not run Oracle’s Unbreakable Enterprise Kernel during the Leapp upgrade. For more information, see Leapp Preupgrade fails on Oracle Linux 8 due to UEK in the ATIX Service Portal.

  7. Perform the Leapp upgrade:

    $ leapp upgrade $ENABLE_REPO_LIST

  8. Reboot your orcharhino Server:

    $ reboot

    After the reboot, a live system conducts the upgrade, reboots to fix SELinux labels, and then reboots into the final EL9 system.

    Part of the Leapp upgrade process takes place after rebooting your orcharhino Server. During the reboot, you cannot connect to orcharhino Server using SSH. Instead, you can use a web console provided by your virtualization solution running orcharhino Server, such as VMware Remote Console.

  9. After the reboot, follow the output of the Leapp upgrade process:

    $ journalctl -u leapp_resume -f

    The Leapp upgrade process must end with leapp_resume.service: Deactivated successfully.. If Leapp reports errors, please contact us.

  10. Verify that orcharhino Server runs on EL9:

    $ cat /etc/os-release | grep "^PRETTY_NAME"

  11. Verify that orcharhino Server is running an EL9 kernel:

    $ uname -r

  12. On AlmaLinux 9 and Rocky Linux 9 only: Remove all no longer required repository files:

    $ find /etc/yum.repos.d -type f -iname "My_Target_OS*.repo" -exec rm {} \; -exec touch {} \;

    Ensure that you set the target OS according to your Leapp upgrade path:

    • On AlmaLinux 8: almalinux

    • On Rocky Linux 8: rocky

  13. On Oracle Linux 9 only: Remove all no longer required repository files:

    $ find /etc/yum.repos.d -type f -iname "*-ol8.repo*" -exec rm {} \;
$ find /etc/yum.repos.d -type f -iname "*-ol9.repo" -exec rm {} \; -exec touch {} \;

  14. Remove all temporary repository file backups:

    $ rm /etc/yum.repos.d/*.repo.*

  15. Update all packages on your orcharhino Server:

    $ dnf upgrade

  16. Configure your orcharhino Server:

    $ orcharhino-installer

  17. Empty the list of protected packages:

    $ dnf config-manager --save --setopt exclude=""

  18. List remaining EL8-specific packages:

    $ rpm -qa | grep -e "\.el[678]" | sort -u

  19. Remove remaining EL8-specific packages:

    $ dnf remove My_Remaining_EL8_Packages

    Use dnf to verify that package dependencies are maintained. Review the transaction before accepting to ensure that no packages are unintentionally removed.

  20. Update the rescue Kernel and initrd on orcharhino Server:

    $ rm /boot/vmlinuz-*rescue* /boot/initramfs-*rescue*
$ /usr/lib/kernel/install.d/51-dracut-rescue.install add "$(uname -r)" /boot "/boot/vmlinuz-$(uname -r)"

  21. Set SELinux to enforcing mode:

    1. Enable enforcing mode:

      $ sed -i 's/SELINUX=.*$/SELINUX=enforcing/g' /etc/selinux/config

    2. Reinstall required packages:

      $ dnf reinstall foreman-selinux katello-selinux orcharhino-selinux

    3. Reconfigure orcharhino Server:

      $ orcharhino-installer
$ touch /.autorelabel

  22. Remove the remaining Leapp packages:

    $ dnf remove leapp-deps-el9 leapp-repository-deps-el9

  23. Reboot your orcharhino Server:

    $ reboot
Verification

  1. On your orcharhino Server, verify that all orcharhino services are running:

    $ orcharhino-maintain service status -b

  2. In the orcharhino management UI, navigate to Administer > About.

  3. In the Backend System Status box, ensure that each component reports status OK.

  4. Verify that the current rescue kernel and initial RAM file system are based on EL9:

    $ lsinitrd /boot/initramfs-*rescue*.img | grep --quiet --max-count=1 "$(uname -r)/kernel/" && echo "Success: Rescue initial RAM file system is based on EL9" || echo "Failure: Rescue initial RAM file system is based on EL8"
$ grubby --info $(ls /boot/vmlinuz-*rescue*) | grep --quiet -E "title\=.*\) 9.[[:digit:]] \(.*" && echo "Success: Rescue kernel is based on EL9" || echo "Failure: Rescue kernel is based on EL8"

  5. Verify that there is no boot entry for EL8:

    $ grubby --info ALL | grep --quiet -E "title\=.*\) 8.[[:digit:]] \(.*" && echo "Failure: EL8 boot entries listed by grubby" || grep -r ".el8" /boot/loader/entries/ && echo "Failure: EL8 boot entries present in /boot/loader/entries/" || echo "Success: No EL8 boot entries found."

  6. Verify that SELinux is in enforcing mode:

    $ getenforce

Upgrading orcharhino Server from EL8 to EL9 in a disconnected environment

Use this procedure if orcharhino Server is not registered to OCC but receives content through a local or remote Yum repository such as file:///mnt/my_disk/orcharhino_7_1/ or https://mirror.example.com/orcharhino_7_1/.

Prerequisites

  • Ensure that your orcharhino Server runs orcharhino 7.1.

  • Ensure that all your orcharhino Proxy Servers run orcharhino 7.1.

  • If you use custom repositories, please contact us on how to migrate them from EL8 to EL9. Note that this is not supported.

  • Ensure that your orcharhino Server has access to the latest orcharhino 7.1 release provided by ATIX AG.

  • Ensure that your orcharhino Server has access to the latest EL8 repositories provided by ATIX AG.

  • Ensure that your orcharhino Server has access to the latest EL9 repositories provided by ATIX AG.

Handling offline scenarios

In disconnected environments, you have to use your custom Yum repositories. Replace the repository IDs in the commands for installing Leapp packages, switching content, running leapp preupgrade, and running leapp upgrade with the repository IDs of your custom Yum repositories. For a list of repository IDs for orcharhino on EL9, see Using custom repository IDs during Leapp upgrades in the ATIX Service Portal. To list all available repositories on orcharhino Server, run dnf repolist all.

Preparing Leapp on EL8

Procedure

  1. Backup your orcharhino Server:

    ATIX AG recommends running orcharhino as a virtual server and performing a system snapshot at this point. For more information, see Backing up orcharhino.

  2. Update all packages on your orcharhino Server:

    $ dnf upgrade

  3. Install Leapp prerequisites on your orcharhino Server:

    $ dnf install pciutils policycoreutils-python-utils python3 python3-requests python3-setuptools systemd-container

  4. Configure your orcharhino Server:

    $ orcharhino-installer

  5. Reindex your database on orcharhino Server:

    $ runuser -u postgres -- reindexdb -a

    For more information, see Leapp Upgrade fails due to error when reindexing the database in the ATIX Service Portal.

  6. Ensure that /boot provides enough free disk space:

    $ df -h /boot

    For more information, see Deleting old Kernels before the Leapp Upgrade to EL9 in the ATIX Service Portal.

  7. Reboot your orcharhino Server:

    $ reboot

  8. Install Leapp on your orcharhino Server:

    $ dnf install --disablerepo=* --enablerepo=ATIX_orcharhino_Server_EL8_orcharhino_7_1 leapp leapp-repository

    Replace the repository ID with your local mirror of the orcharhino 7.1 repository. To list all available repositories on orcharhino Server, run dnf repolist all.

Switching content

Switch content from EL8 to EL9 on your orcharhino Server.

Procedure

  1. On your orcharhino Server, create repository files for EL9 content that point to your local or remote Yum repositories.

  2. List all available repositories on orcharhino Server:

    $ dnf repolist all

    Note down all repository IDs.

  3. Disable all EL8 repositories:

    $ dnf config-manager --disable My_Custom_EL8_Repository_ID_1 --disable My_Custom_EL8_Repository_ID_2

  4. Enable all EL9 repositories:

    $ dnf config-manager --enable My_Custom_EL9_Repository_ID_1 --enable My_Custom_EL9_Repository_ID_2

Running Leapp

If you upgrade orcharhino Server in a disconnected environment, you have to enable all EL9 repositories using their repository IDs during the Leapp preupgrade and upgrade steps. You can view all currently present repository IDs using find /etc/yum.repos.d/ -type f -name "*.repo" | xargs grep --no-filename "^\[" | sort -u. Specify each EL9 repository for all leapp preupgrade and leapp upgrade commands using --enablerepo=My_Custom_EL9_Repository_ID.

Procedure

  1. Perform Leapp pre-upgrade checks:

    $ leapp preupgrade --enablerepo=_My_Custom_EL9_Repository_ID_1_ --enablerepo=_My_Custom_EL9_Repository_ID_2_

    The Leapp pre-upgrade check reports inhibitors that prevent the Leapp upgrade on orcharhino Server. Examine the report in the /var/log/leapp/leapp-report.txt file and have a look at the most common remediation instructions in Leapp Preupgrade Reports. If you encounter any additional issues, please have a look at Upgrading orcharhino from EL8 to EL9 or contact the orcharhino support team.

  2. After resolving all Leapp upgrade inhibitors, rerun the Leapp pre-upgrade check:

    $ leapp preupgrade --enablerepo=_My_Custom_EL9_Repository_ID_1_ --enablerepo=_My_Custom_EL9_Repository_ID_2_

    If Leapp reports issues, please contact us.

  3. On Oracle Linux 8 only: Ensure that your orcharhino Server does not run Oracle’s Unbreakable Enterprise Kernel during the Leapp upgrade. For more information, see Leapp Preupgrade fails on Oracle Linux 8 due to UEK in the ATIX Service Portal.

  4. Perform the Leapp upgrade:

    $ leapp upgrade --enablerepo=_My_Custom_EL9_Repository_ID_1_ --enablerepo=_My_Custom_EL9_Repository_ID_2_

  5. Reboot your orcharhino Server:

    $ reboot

    After the reboot, a live system conducts the upgrade, reboots to fix SELinux labels, and then reboots into the final EL9 system.

    Part of the Leapp upgrade process takes place after rebooting your orcharhino Server. During the reboot, you cannot connect to orcharhino Server using SSH. Instead, you can use a web console provided by your virtualization solution running orcharhino Server, such as VMware Remote Console.

  6. After the reboot, follow the output of the Leapp upgrade process:

    $ journalctl -u leapp_resume -f

    The Leapp upgrade process must end with leapp_resume.service: Deactivated successfully.. If Leapp reports errors, please contact us.

  7. Verify that orcharhino Server runs on EL9:

    $ cat /etc/os-release | grep "^PRETTY_NAME"

  8. Verify that orcharhino Server is running an EL9 kernel:

    $ uname -r

  9. On AlmaLinux 9 and Rocky Linux 9 only: Remove all no longer required repository files:

    $ find /etc/yum.repos.d -type f -iname "My_Target_OS*.repo" -exec rm {} \; -exec touch {} \;

    Ensure that you set the target OS according to your Leapp upgrade path:

    • On AlmaLinux 8: almalinux

    • On Rocky Linux 8: rocky

  10. On Oracle Linux 9 only: Remove all no longer required repository files:

    $ find /etc/yum.repos.d -type f -iname "*-ol8.repo*" -exec rm {} \;
$ find /etc/yum.repos.d -type f -iname "*-ol9.repo" -exec rm {} \; -exec touch {} \;

  11. Remove all temporary repository file backups:

    $ rm /etc/yum.repos.d/*.repo.*

  12. Update all packages on your orcharhino Server:

    $ dnf upgrade

  13. Configure your orcharhino Server:

    $ orcharhino-installer

  14. Empty the list of protected packages:

    $ dnf config-manager --save --setopt exclude=""

  15. List remaining EL8-specific packages:

    $ rpm -qa | grep -e "\.el[678]" | sort -u

  16. Remove remaining EL8-specific packages:

    $ dnf remove My_Remaining_EL8_Packages

    Use dnf to verify that package dependencies are maintained. Review the transaction before accepting to ensure that no packages are unintentionally removed.

  17. Update the rescue Kernel and initrd on orcharhino Server:

    $ rm /boot/vmlinuz-*rescue* /boot/initramfs-*rescue*
$ /usr/lib/kernel/install.d/51-dracut-rescue.install add "$(uname -r)" /boot "/boot/vmlinuz-$(uname -r)"

  18. Set SELinux to enforcing mode:

    1. Enable enforcing mode:

      $ sed -i 's/SELINUX=.*$/SELINUX=enforcing/g' /etc/selinux/config

    2. Reinstall required packages:

      $ dnf reinstall foreman-selinux katello-selinux orcharhino-selinux

    3. Reconfigure orcharhino Server:

      $ orcharhino-installer
$ touch /.autorelabel

  19. Remove the remaining Leapp packages:

    $ dnf remove leapp-deps-el9 leapp-repository-deps-el9

  20. Reboot your orcharhino Server:

    $ reboot
Verification

  1. On your orcharhino Server, verify that all orcharhino services are running:

    $ orcharhino-maintain service status -b

  2. In the orcharhino management UI, navigate to Administer > About.

  3. In the Backend System Status box, ensure that each component reports status OK.

  4. Verify that the current rescue kernel and initial RAM file system are based on EL9:

    $ lsinitrd /boot/initramfs-*rescue*.img | grep --quiet --max-count=1 "$(uname -r)/kernel/" && echo "Success: Rescue initial RAM file system is based on EL9" || echo "Failure: Rescue initial RAM file system is based on EL8"
$ grubby --info $(ls /boot/vmlinuz-*rescue*) | grep --quiet -E "title\=.*\) 9.[[:digit:]] \(.*" && echo "Success: Rescue kernel is based on EL9" || echo "Failure: Rescue kernel is based on EL8"

  5. Verify that there is no boot entry for EL8:

    $ grubby --info ALL | grep --quiet -E "title\=.*\) 8.[[:digit:]] \(.*" && echo "Failure: EL8 boot entries listed by grubby" || grep -r ".el8" /boot/loader/entries/ && echo "Failure: EL8 boot entries present in /boot/loader/entries/" || echo "Success: No EL8 boot entries found."

  6. Verify that SELinux is in enforcing mode:

    $ getenforce

Upgrading orcharhino Proxy Servers from EL8 to EL9

orcharhino Proxy Servers consume the same content as orcharhino Server. During the orcharhino 7.1 lifecycle, you have to upgrade all orcharhino Proxy Servers from EL8 to EL9.

Prerequisites

  • Ensure that your orcharhino Server runs orcharhino 7.1.

  • Ensure that all your orcharhino Proxy Servers run orcharhino 7.1.

  • If you use custom repositories, please contact us on how to migrate them from EL8 to EL9. Note that this is not supported.

  • Ensure that your orcharhino Proxy Server has access to the latest orcharhino 7.1 release provided by ATIX AG.

  • Ensure that your orcharhino Proxy Server has access to the latest EL8 repositories provided by ATIX AG.

  • Ensure that your orcharhino Proxy Server has access to the latest EL9 repositories provided by ATIX AG.

Preparing Leapp on EL8

Procedure

  1. Backup your orcharhino Proxy Server:

    ATIX AG recommends running orcharhino as a virtual server and performing a system snapshot at this point. For more information, see Backing up orcharhino.

  2. If one or more of your orcharhino Proxy Servers already run on EL9:

    1. In your orcharhino Proxy content view, delete all content view versions that contain repositories with EL9 packages.

    2. Publish and promote a new content view version with EL8 repositories.

  3. Update all packages on your orcharhino Proxy Server:

    $ dnf upgrade

  4. Install Leapp prerequisites on your orcharhino Proxy Server:

    $ dnf install pciutils policycoreutils-python-utils python3 python3-requests python3-setuptools systemd-container

  5. Configure your orcharhino Proxy Server:

    $ orcharhino-installer

  6. Reindex your database on orcharhino Proxy Server:

    $ runuser -u postgres -- reindexdb -a

    For more information, see Leapp Upgrade fails due to error when reindexing the database in the ATIX Service Portal.

  7. Ensure that /boot provides enough free disk space:

    $ df -h /boot

    For more information, see Deleting old Kernels before the Leapp Upgrade to EL9 in the ATIX Service Portal.

  8. Reboot your orcharhino Proxy Server:

    $ reboot

  9. Install Leapp on your orcharhino Proxy Server:

    $ dnf install --disablerepo=* --enablerepo=ATIX_orcharhino_Server_EL8_orcharhino_7_1 leapp leapp-repository

    Replace the repository ID with the repository ID for orcharhino 7.1 provided by your orcharhino Server. To list all available repositories on orcharhino Proxy Server, run dnf repolist all.

Updating content

Update the content provided by orcharhino Server to your orcharhino Proxy Servers.

Prepare the Leapp upgrade on all your orcharhino Proxy Servers before providing EL9 content using /opt/orcharhino/automation/play_orcharhino_proxy_content.sh as described in Providing content for orcharhino Proxy Server. Otherwise, subsequent orcharhino Proxy Servers cannot access and install the required EL8 packages from orcharhino Server.

If you cannot prepare the Leapp upgrade on all your orcharhino Proxy Servers before performing the Leapp upgrade on your first orcharhino Proxy Server, you have to roll back to the last content view version of the orcharhino Proxy content view that still contains repositories with EL8 packages when preparing the Leapp upgrade on subsequent orcharhino Proxy Servers.
Procedure

  1. On Oracle Linux 9 in disconnected environments only: Update the OracleLinux Client 9 repository to consume content from your local or remote Yum repository for the orcharhino Client for Oracle Linux 9.

    1. In the orcharhino management UI, navigate to Content > Products.

    2. Select the orcharhino Proxy product.

    3. On the Repositories tab, select the OracleLinux Client 9 repository.

    4. In the Upstream URL field, enter the URL of your local or remote Yum repository for the orcharhino Client for Oracle Linux 9.

    5. From the Select Action menu, click Sync Now to synchronize the repository.

    6. Navigate to Content > Lifecycle > Content Views.

    7. Select the orcharhino Proxy content view.

    8. Click Publish new version to publish a new version of the content view.

    For more information, see Providing content for orcharhino Proxy Server in Upgrading orcharhino Proxy.

  2. List all available EL9 repositories on orcharhino Proxy Server:

    $ dnf repolist all

  3. Enable the EL9 repositories on your orcharhino Proxy Server:

    $ subscription-manager repos --enable My_Custom_EL9_Repository_ID_1 --enable My_Custom_EL9_Repository_ID_2

  4. Optional: Verify the status of the EL9 repositories on orcharhino Proxy Server:

    $ dnf repolist all

Running Leapp

Procedure

  1. Set the ENABLE_REPO_LIST environment variable on your orcharhino Proxy Server:

    $ export ENABLE_REPO_LIST="$(LANG=C subscription-manager repos --list-enabled | grep '^Repo ID:' | awk '{print $3}' | sed 's/^/--enablerepo=/g' | tr '\n' ' ' | xargs)"

  2. On Oracle Linux 8 only: Extend the ENABLE_REPO_LIST environment variable:

    $ export ENABLE_REPO_LIST="$ENABLE_REPO_LIST --enablerepo=My_Repository_ID"

    Replace My_Repository_ID with the repository ID of your orcharhino Client for Oracle Linux 9 repository.

  3. Perform Leapp pre-upgrade checks:

    $ leapp preupgrade $ENABLE_REPO_LIST

    The Leapp pre-upgrade check reports inhibitors that prevent the Leapp upgrade on orcharhino Proxy Server. Examine the report in the /var/log/leapp/leapp-report.txt file and have a look at the most common remediation instructions in Leapp Preupgrade Reports. If you encounter any additional issues, please have a look at Upgrading orcharhino from EL8 to EL9 or contact the orcharhino support team.

  4. After resolving all Leapp upgrade inhibitors, rerun the Leapp pre-upgrade check:

    $ leapp preupgrade $ENABLE_REPO_LIST

    If Leapp reports issues, please contact us.

  5. On Oracle Linux 8 only: Ensure that your orcharhino Proxy Server does not run Oracle’s Unbreakable Enterprise Kernel during the Leapp upgrade. For more information, see Leapp Preupgrade fails on Oracle Linux 8 due to UEK in the ATIX Service Portal.

  6. Perform the Leapp upgrade:

    $ leapp upgrade $ENABLE_REPO_LIST

  7. Reboot your orcharhino Proxy Server:

    $ reboot

    After the reboot, a live system conducts the upgrade, reboots to fix SELinux labels, and then reboots into the final EL9 system.

    Part of the Leapp upgrade process takes place after rebooting your orcharhino Proxy Server. During the reboot, you cannot connect to orcharhino Proxy Server using SSH. Instead, you can use a web console provided by your virtualization solution running orcharhino Proxy Server, such as VMware Remote Console.

  8. After the reboot, follow the output of the Leapp upgrade process:

    $ journalctl -u leapp_resume -f

    The Leapp upgrade process must end with leapp_resume.service: Deactivated successfully.. If Leapp reports errors, please contact us.

  9. Verify that orcharhino Proxy Server runs on EL9:

    $ cat /etc/os-release | grep "^PRETTY_NAME"

  10. Verify that orcharhino Proxy Server is running an EL9 kernel:

    $ uname -r

  11. On AlmaLinux 9 and Rocky Linux 9 only: Remove all no longer required repository files:

    $ find /etc/yum.repos.d -type f -iname "My_Target_OS*.repo" -exec rm {} \; -exec touch {} \;

    Ensure that you set the target OS according to your Leapp upgrade path:

    • On AlmaLinux 8: almalinux

    • On Rocky Linux 8: rocky

  12. On Oracle Linux 9 only: Remove all no longer required repository files:

    $ find /etc/yum.repos.d -type f -iname "*-ol8.repo*" -exec rm {} \;
$ find /etc/yum.repos.d -type f -iname "*-ol9.repo" -exec rm {} \; -exec touch {} \;

  13. Remove all temporary repository file backups:

    $ rm /etc/yum.repos.d/*.repo.*

  14. Update all packages on your orcharhino Proxy Server:

    $ dnf upgrade

  15. Configure your orcharhino Proxy Server:

    $ orcharhino-installer

  16. Empty the list of protected packages:

    $ dnf config-manager --save --setopt exclude=""

  17. List remaining EL8-specific packages:

    $ rpm -qa | grep -e "\.el[678]" | sort -u

  18. Remove remaining EL8-specific packages:

    $ dnf remove My_Remaining_EL8_Packages

    Use dnf to verify that package dependencies are maintained. Review the transaction before accepting to ensure that no packages are unintentionally removed.

  19. Update the rescue Kernel and initrd on orcharhino Proxy Server:

    $ rm /boot/vmlinuz-*rescue* /boot/initramfs-*rescue*
$ /usr/lib/kernel/install.d/51-dracut-rescue.install add "$(uname -r)" /boot "/boot/vmlinuz-$(uname -r)"

  20. Set SELinux to enforcing mode:

    1. Enable enforcing mode:

      $ sed -i 's/SELINUX=.*$/SELINUX=enforcing/g' /etc/selinux/config

    2. Reinstall required packages:

      $ dnf reinstall foreman-selinux

    3. Reconfigure orcharhino Proxy Server:

      $ orcharhino-installer
$ touch /.autorelabel

  21. Remove the remaining Leapp packages:

    $ dnf remove leapp-deps-el9 leapp-repository-deps-el9

  22. Reboot your orcharhino Proxy Server:

    $ reboot
Verification

  1. On your orcharhino Proxy Server, verify that all orcharhino Proxy services are running:

    $ systemctl status foreman-proxy.service

  2. In the orcharhino management UI, navigate to Infrastructure > orcharhino Proxies.

  3. Select your orcharhino Proxy Server.

  4. Ensure that the table specifies No Failed Features.

  5. Verify that the current rescue kernel and initial RAM file system are based on EL9:

    $ lsinitrd /boot/initramfs-*rescue*.img | grep --quiet --max-count=1 "$(uname -r)/kernel/" && echo "Success: Rescue initial RAM file system is based on EL9" || echo "Failure: Rescue initial RAM file system is based on EL8"
$ grubby --info $(ls /boot/vmlinuz-*rescue*) | grep --quiet -E "title\=.*\) 9.[[:digit:]] \(.*" && echo "Success: Rescue kernel is based on EL9" || echo "Failure: Rescue kernel is based on EL8"

  6. Verify that there is no boot entry for EL8:

    $ grubby --info ALL | grep --quiet -E "title\=.*\) 8.[[:digit:]] \(.*" && echo "Failure: EL8 boot entries listed by grubby" || grep -r ".el8" /boot/loader/entries/ && echo "Failure: EL8 boot entries present in /boot/loader/entries/" || echo "Success: No EL8 boot entries found."

  7. Verify that SELinux is in enforcing mode:

    $ getenforce