Upgrading orcharhino 6.3 from EL7 to EL8

This guide describes how you can upgrade the base OS of orcharhino 6.3 from EL7 to EL8.

Before you can start the Leapp upgrade process from EL7 to EL8, ensure that you have a valid orcharhino Subscription Key for EL8. If this is not yet the case, please contact sales@orcharhino.com and request an orcharhino Subscription Key for EL8 for your orcharhino.

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

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

ATIX does not support using third party repositories on your orcharhino Server or orcharhino Proxies. 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.

Leapp Upgrade Paths

You can run orcharhino 6.3 on CentOS 7, Oracle Linux 7, and Red Hat Enterprise Linux 7. From EL7, orcharhino supports the following Leapp upgrade paths:

CentOS 7 > Alma Linux 8
Oracle Linux 7 > Oracle Linux 8
Red Hat Enterprise Linux 7 > Red Hat Enterprise Linux 8

Upgrading orcharhino Server from EL7 to EL8

Use this procedure to upgrade orcharhino Server 6.3 from EL7 to EL8. Note that the Leapp upgrade process results in downtime of orcharhino.

Prerequisites

Ensure your orcharhino Server is running orcharhino 6.3.
Ensure all your orcharhino Proxies are running orcharhino 6.3.
Ensure you have your orcharhino Subscription Key for EL8.
If you are using custom repositories, please contact us on how to migrate them from EL7 to EL8. Note that this is not supported.

Preparing Leapp

Procedure

Backup your orcharhino Server:

We generally recommend running orcharhino as a virtual server and performing a system snapshot at this point. For more information, see backing up orcharhino.
Update all packages on your orcharhino Server:
```
# yum update
```
Reboot your orcharhino Server:
```
# reboot
```
On Oracle Linux 7 only: Add the Oracle Linux 7 DNF repository as /etc/yum.repos.d/ol_7_dnf.repo:
```
[ol_7_dnf]
name=Oracle Linux 7 DNF
baseurl= URL_to_DNF_for_Oracle_Linux_7
enabled=1
gpgcheck=0
repo_gpgcheck=0
```
Use the Published At URL as baseurl on your orcharhino Server from the Oracle Linux 7 DNF repository on your orcharhino Server.
Install Leapp on your orcharhino Server:
```
# yum install dnf python-requests
# yum install \
  --disablerepo=* \
  --enablerepo=ATIX_P_orcharhino_6_3_release_R_orcharhino_6_3_release \
  leapp leapp-repository leapp-data-My_Target_OS
```
The name of the package depends on your Leapp upgrade path:
- On CentOS 7: leapp-data-almalinux
- On Oracle Linux 7: leapp-data-oraclelinux
- On Red Hat Enterprise Linux 7: leapp-data-rhel

If you use Puppet 6, you have to adjust the repository mapping for Leapp:

# sed -i 's/"ATIX_Puppet_for_EL8_Puppet_7_for_EL8"/"ATIX_Puppet_for_EL8_Puppet_6_for_EL8"/g' /etc/leapp/files/pes-events.json
# sed -i 's/"ATIX_Puppet_for_EL8_Puppet_7_for_EL8"/"ATIX_Puppet_for_EL8_Puppet_6_for_EL8"/g' /etc/leapp/files/repomap.json
# sed -i 's/"ATIX_P_Puppet7_R_Puppet7"/"ATIX_P_Puppet6_R_Puppet6"/g' /etc/leapp/files/pes-events.json
# sed -i 's/"ATIX_P_Puppet7_R_Puppet7"/"ATIX_P_Puppet6_R_Puppet6"/g' /etc/leapp/files/repomap.json

Without these adjustments, orcharhino upgrades Puppet 6 to Puppet 7 during the Leapp upgrade process. orcharhino supports running Puppet 6 or 7, but not all of your custom Puppet modules might be compatible with both Puppet 6 and Puppet 7.

Registering to OCC

Procedure

In the orcharhino management UI, enter your orcharhino Subscription Key for orcharhino on EL8.

Enable the new repository definitions for OCC:

# orcharhino-maintain advanced procedure run switch-repo-mappings

Ensure that dnf uses HTTP proxy settings similar to yum. For reference, you can consult the yum.conf on your orcharhino Server.
```
# grep "^proxy\|^proxy_username\|^proxy_password" /etc/yum.conf
```
Register your orcharhino Server to OCC:
```
# orcharhino-maintain advanced procedure run switch-acc
```
If you use a firewall, set the relevant rules for the new IP address. For more information, see Registering orcharhino Server to OCC.

If you experience failures during re-registration, see Cannot register orcharhino Server to orcharhino Customer Center (OCC) due to subscription-manager error.
Enable the required EL8 repositories for your orcharhino Server:
```
# orcharhino-maintain advanced procedure run repositories-setup \
  --version 6.3 \
  --distro-version 8 \
  --distro-name My_Target_OS
```
Ensure to set the target OS according to your Leapp upgrade path:
- On CentOS 7: almalinux
- On Oracle Linux 7: oracle
- On Red Hat Enterprise Linux 7: redhat

Ensure the specified --distro-name is the same as the one your orcharhino Subscription Key was created for.

Running Leapp

Procedure

On Oracle Linux 7 only: Set the ENABLE_REPO_LIST environment variable:
```
# export ENABLE_REPO_LIST="--enablerepo=orcharhino_Oracle_8_Client"
```

Set the ENABLE_REPO_LIST environment variable:

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

Perform Leapp pre-upgrade checks:
```
# leapp preupgrade $ENABLE_REPO_LIST
```
Note that the Leapp pre-upgrade check is expected to fail during the first run, but report issues and inhibit the upgrade. Examine the report in the /var/log/leapp/leapp-report.txt file, answer all questions using leapp answer, and manually resolve the other reported problems. If you encounter any additional issues, please have a look at the orcharhino Knowledge Base or contact the orcharhino support team.
On Red Hat Enterprise Linux 7 only: Remove a no longer required Kernel module:
```
# rmmod pata_acpi
```

Provide answers to the Leapp upgrade process:

# leapp answer --section remove_pam_pkcs11_module_check.confirm=True

Rerun the Leapp pre-upgrade checks:
```
# leapp preupgrade $ENABLE_REPO_LIST
```
If Leapp reports issues, please contact us.
On Oracle Linux 7 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 7 due to UEK in the ATIX Service Portal.
On Oracle Linux 7 only: Ensure uname26 is not installed:
```
# yum remove uname26
```
Perform the Leapp upgrade:
```
# leapp upgrade $ENABLE_REPO_LIST
```

Reboot your orcharhino Server:

# reboot

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.

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: Succeeded.. If Leapp reports errors, please contact us.

On Alma Linux 8 only: Remove all no longer required repository files:

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

On Oracle Linux 8 only: Remove all no longer required repository files:

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

Remove all temporary repository file backups:
```
# rm /etc/yum.repos.d/*.original
```
Configure orcharhino Server:
```
# orcharhino-installer
```

Reindex the PostgreSQL database:

# cd /
# runuser -u postgres -- reindexdb -a

Update all packages on your orcharhino Server:
```
# dnf update
```

Empty the list of protected packages:

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

List remaining EL7-specific packages:

# rpm -qa | grep -e "\.el[67]" | grep -vE "^(gpg-pubkey|libmodulemd|katello-ca-consumer|subscription-manager)" | sort -u

Remove remaining EL7-specific packages:
```
# dnf remove My_Remaining_EL7_Packages
```

List and remove old Kernels on your orcharhino Server:

# grubby --info=ALL | grep "\.el7"
# /bin/kernel-install remove My_Old_Kernel_Version

Optional: If you require SELinux to be in enforcing mode, perform the following steps:
1. Set SELinux=enforcing in /etc/selinux/config.
2. Reinstall required packages:
  # dnf reinstall foreman-selinux katello-selinux orcharhino-selinux
3. Reconfigure orcharhino Server:
  # orcharhino-installer # touch /.autorelabel
Reboot your orcharhino Server:
```
# reboot
```
Verify all orcharhino services are running:
```
# hammer ping
```
Navigate to Administer > About and check the Backend System Status. Ensure the box lists each component with status OK.

Upgrading orcharhino Server from EL7 to EL8 in a Disconnected Environment

If your orcharhino Server is not registered with ATIX ACC but receives content through a local or remote repository, you have to manually adjust the repository IDs before starting the Leapp upgrade process. Use this procedure if orcharhino Server consumes a local Yum repository such as file:///mnt/my_disk/orcharhino_release_6.3/ or a remote Yum repository such as http://mirror.example.com/orcharhino_release_6.3 with custom repository IDs.

Prerequisites

Ensure your orcharhino Server is running orcharhino 6.3.
Ensure all your orcharhino Proxies are running orcharhino 6.3.
Ensure you have your orcharhino Subscription Key for EL8.
If you are using custom repositories, please contact us on how to migrate them from EL7 to EL8. Note that this is not supported.
Ensure your orcharhino Server has access to the latest orcharhino 6.3 release provided by ATIX.
Ensure your orcharhino Server has access to the latest EL7 repositories provided by ATIX.
Ensure your orcharhino Server has access to the latest EL8 repositories provided by ATIX.

Preparing Leapp

Procedure

Backup your orcharhino Server:

We generally recommend running orcharhino as a virtual server and performing a system snapshot at this point. For more information, see backing up orcharhino.
Update all packages on your orcharhino Server:
```
# yum update
```
Reboot your orcharhino Server:
```
# reboot
```
On Oracle Linux 7 only: Add the Oracle Linux 7 DNF repository as /etc/yum.repos.d/ol_7_dnf.repo:
```
[ol_7_dnf]
name=Oracle Linux 7 DNF
baseurl= URL_to_DNF_for_Oracle_Linux_7
enabled=1
gpgcheck=0
repo_gpgcheck=0
```
Use the Published At URL as baseurl on your orcharhino Server from the Oracle Linux 7 DNF repository on your orcharhino Server.
Install Leapp on your orcharhino Server:
```
# yum install dnf python-requests
# yum install \
  --disablerepo=* \
  --enablerepo=ATIX_P_orcharhino_6_3_release_R_orcharhino_6_3_release \
  leapp leapp-repository leapp-data-My_Target_OS
```
Replace the repository ID with your local mirror of the orcharhino 6.3 repository.

The name of the package depends on your Leapp upgrade path:
- On CentOS 7: leapp-data-almalinux
- On Oracle Linux 7: leapp-data-oraclelinux
- On Red Hat Enterprise Linux 7: leapp-data-rhel
Enable module_hotfixes for your orcharhino 6.3 repository:
```
# sed -i '/\[ATIX_P_orcharhino_6_3_release_EL8_R_orcharhino_6_3_release_EL8\]/amodule_hotfixes\=1' /etc/yum.repos.d/redhat.repo
```
Replace the repository ID with your local mirror of the orcharhino 6.3 repository.

Switching Content

Switch content from EL7 to EL8 on your orcharhino Server.

Procedure

Optional: List all available repositories on orcharhino Server:
```
# yum repolist all
```

Disable all EL7 repositories and enable all EL8 repositories:

# yum-config-manager \
  --disable My_EL7_Repository_1 \
  --disable My_EL7_Repository_2
# yum-config-manager \
  --enable My_EL8_Repository_1 \
  --enable My_EL8_Repository_2

Handling Offline Scenarios

Replace the default repository IDs to match your custom repository IDs in /etc/leapp/files/pes-events.json and /etc/leapp/files/repomap.json. Replace Default_Repository_ID for all repositories required for orcharhino: all common repository IDs and all OS-specific repository IDs:

# sed -i 's/"Default_Repository_ID"/"My_Custom_Repository_ID"/g' /etc/leapp/files/pes-events.json
# sed -i 's/"Default_Repository_ID"/"My_Custom_Repository_ID"/g' /etc/leapp/files/repomap.json

For a list of all repository IDs, see Using Custom Repository IDs during Leapp Upgrade in the ATIX Service Portal.

Running Leapp

If you upgrade orcharhino Server in a disconnected environment, you have to enable all EL8 repositories using their repo ID 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 EL8 repository for all leapp preupgrade and leapp upgrade commands using --enablerepo=My_Custom_EL8_Repository_ID.

Procedure

Perform Leapp pre-upgrade checks:
```
# leapp preupgrade --no-rhsm --enablerepo=_My_Custom_EL8_Repository_ID_1_ --enablerepo=_My_Custom_EL8_Repository_ID_2_
```
Note that the Leapp pre-upgrade check is expected to fail during the first run, but report issues and inhibit the upgrade. Examine the report in the /var/log/leapp/leapp-report.txt file, answer all questions using leapp answer, and manually resolve the other reported problems. If you encounter any additional issues, please have a look at the orcharhino Knowledge Base or contact the orcharhino support team.
On Red Hat Enterprise Linux 7 only: Remove a no longer required Kernel module:
```
# rmmod pata_acpi
```

Provide answers to the Leapp upgrade process:

# leapp answer --section remove_pam_pkcs11_module_check.confirm=True

Rerun the Leapp pre-upgrade checks:

# leapp preupgrade --no-rhsm --enablerepo=_My_Custom_EL8_Repository_ID_1_ --enablerepo=_My_Custom_EL8_Repository_ID_2_

If Leapp reports issues, please contact us.

On Oracle Linux 7 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 7 due to UEK in the ATIX Service Portal.
On Oracle Linux 7 only: Ensure uname26 is not installed:
```
# yum remove uname26
```

Perform the Leapp upgrade:

# leapp upgrade --no-rhsm --enablerepo=_My_Custom_EL8_Repository_ID_1_ --enablerepo=_My_Custom_EL8_Repository_ID_2_

Reboot your orcharhino Server:

# reboot

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: Succeeded.. If Leapp reports errors, please contact us.

On Alma Linux 8 only: Remove all no longer required repository files:

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

On Oracle Linux 8 only: Remove all no longer required repository files:

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

Remove all temporary repository file backups:
```
# rm /etc/yum.repos.d/*.original
```
Configure orcharhino Server:
```
# orcharhino-installer
```

Reindex the PostgreSQL database:

# cd /
# runuser -u postgres -- reindexdb -a

Update all packages on your orcharhino Server:
```
# dnf update
```

Empty the list of protected packages:

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

List remaining EL7-specific packages:

# rpm -qa | grep -e "\.el[67]" | grep -vE "^(gpg-pubkey|libmodulemd|katello-ca-consumer|subscription-manager)" | sort -u

Remove remaining EL7-specific packages:
```
# dnf remove My_Remaining_EL7_Packages
```

List and remove old Kernels on your orcharhino Server:

# grubby --info=ALL | grep "\.el7"
# /bin/kernel-install remove My_Old_Kernel_Version

Optional: If you require SELinux to be in enforcing mode, perform the following steps:
1. Set SELinux=enforcing in /etc/selinux/config.
2. Reinstall required packages:
  # dnf reinstall foreman-selinux katello-selinux orcharhino-selinux
3. Reconfigure orcharhino Server:
  # orcharhino-installer # touch /.autorelabel
Reboot your orcharhino Server:
```
# reboot
```
Verify all orcharhino services are running:
```
# hammer ping
```
Navigate to Administer > About and check the Backend System Status. Ensure the box lists each component with status OK.

Upgrading orcharhino Proxies from EL7 to EL8

orcharhino Proxies consume the same content as orcharhino Server. During the orcharhino 6.3 lifecycle, you have to upgrade orcharhino Proxies on EL7 to EL8 using Leapp or redeploy them. You have to manually adjust the repository IDs before starting the Leapp upgrade process.

Prerequisites

Ensure your orcharhino Server is running orcharhino 6.3.
Ensure all your orcharhino Proxies are running orcharhino 6.3.
Ensure you have your orcharhino Subscription Key for EL8.
If you are using custom repositories, please contact us on how to migrate them from EL7 to EL8. Note that this is not supported.
Ensure your orcharhino Proxy has access to the latest orcharhino 6.3 release provided by ATIX.
Ensure your orcharhino Proxy has access to the latest EL7 repositories provided by ATIX.
Ensure your orcharhino Proxy has access to the latest EL8 repositories provided by ATIX.
Ensure your orcharhino Proxy is running orcharhino 6.3. For more information, see Providing Content for orcharhino Proxy and Performing the Upgrade in Upgrading orcharhino Proxy.

Preparing Leapp

Procedure

Backup your orcharhino Proxy:

We generally recommend running orcharhino as a virtual server and performing a system snapshot at this point. For more information, see backing up orcharhino.
If one or more of your orcharhino Proxies already run on EL8:
1. In your Smart Proxy Atix content view, delete all content view versions that contain repositories with EL8 packages.
2. Publish and promote a new content view version with EL7 repositories.
Update all packages on your orcharhino Proxy:
```
# yum update
```
Reboot your orcharhino Proxy:
```
# reboot
```
On Oracle Linux 7 only: Add the Oracle Linux 7 DNF repository as /etc/yum.repos.d/ol_7_dnf.repo:
```
[ol_7_dnf]
name=Oracle Linux 7 DNF
baseurl= URL_to_DNF_for_Oracle_Linux_7
enabled=1
gpgcheck=0
repo_gpgcheck=0
```
Use the Published At URL as baseurl on your orcharhino Proxy from the Oracle Linux 7 DNF repository on your orcharhino Server. After upgrading all Oracle Linux based orcharhino Proxies to EL8, you can remove the Oracle Linux 7 DNF repository from your orcharhino Server.
Install Leapp on your orcharhino Proxy:
```
# yum install dnf python-requests
# yum install \
  --disablerepo=* \
  --enablerepo=ATIX_P_orcharhino_6_3_release_R_orcharhino_6_3_release \
  leapp leapp-repository leapp-data-My_Target_OS
```
Replace the repository ID with the repository ID for orcharhino 6.3 provided by your orcharhino Server.

The name of the package depends on your Leapp upgrade path:
- On CentOS 7: leapp-data-almalinux
- On Oracle Linux 7: leapp-data-oraclelinux
- On Red Hat Enterprise Linux 7: leapp-data-rhel

If you use Puppet 6, you have to adjust the repository mapping for Leapp:

# sed -i 's/"ATIX_Puppet_for_EL8_Puppet_7_for_EL8"/"ATIX_Puppet_for_EL8_Puppet_6_for_EL8"/g' /etc/leapp/files/pes-events.json
# sed -i 's/"ATIX_Puppet_for_EL8_Puppet_7_for_EL8"/"ATIX_Puppet_for_EL8_Puppet_6_for_EL8"/g' /etc/leapp/files/repomap.json
# sed -i 's/"ATIX_P_Puppet7_R_Puppet7"/"ATIX_P_Puppet6_R_Puppet6"/g' /etc/leapp/files/pes-events.json
# sed -i 's/"ATIX_P_Puppet7_R_Puppet7"/"ATIX_P_Puppet6_R_Puppet6"/g' /etc/leapp/files/repomap.json

Updating Content

Update the content provided from orcharhino Server to your orcharhino Proxies.

Prepare the Leapp upgrade on all your orcharhino Proxies before providing EL8 content using the orcharhino Proxy Content job template as described in Providing Content for orcharhino Proxy. Otherwise, subsequent orcharhino Proxies cannot access and install the required EL7 packages from orcharhino Server.

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

Procedure

On Oracle Linux 8 only: Add the orcharhino Client for Oracle Linux 8 to your Smart Proxy Atix content view.

If you have not synchronized the orcharhino Client for Oracle Linux 8 yet, synchronize the orcharhino Client for Oracle Linux 8. For more information, see Adding orcharhino Clients for Oracle Linux in Managing Content. Ensure that you use the Upstream URL for orcharhino Client for Oracle Linux 8 from ATIX Service Portal.
Create and publish a content view that contains all required repositories for EL8. For more information, see Providing Content for orcharhino Proxy in Upgrading orcharhino Proxy.
Update the Yum cache on orcharhino Proxy:
```
# yum makecache
```
Enable module_hotfixes for your orcharhino 6.3 repository:
```
# subscription-manager repo-override \
  --repo My_Organization_Smart_Proxy_Atix_ATIX_orcharhino_Server_EL8_orcharhino_6_3 \
  --add module_hotfixes:1
```
Ensure that you replace the repository ID with the repository ID for orcharhino 6.3 provided by your orcharhino Server.
Optional: List all available repositories on orcharhino Proxy:
```
# yum repolist all
```

Adjusting Leapp for orcharhino Proxies

If you provide content to orcharhino Proxies from orcharhino Server using the orcharhino Configuration - orcharhino Proxy Content job template, follow the procedure below to replace all repository IDs within /etc/leapp/files/pes-events.json and /etc/leapp/files/repomap.json.

If you provide content to orcharhino Proxies using custom repositories, you have to manually replace the default repository IDs. For more information, see Handling Offline Scenarios.

Procedure

Adjust the repository IDs used by Leapp on your orcharhino Proxy:
```
# /usr/bin/or_proxy_prepare_leapp "My_Organization_Label"
```
On Oracle Linux 7 only: Determine the repository ID of your orcharhino Client for Oracle Linux 8 repository:
```
# subscription-manager repos --list-enabled
```
Search for the orcharhino Client for Oracle Linux 8 repository in the output and note down the repository ID.
On Oracle Linux 7 only: Set the repository ID of your orcharhino Client for Oracle Linux 8 repository in /etc/leapp/files/repomap.json:
```
# sed -i "s/orcharhino_Oracle_8_Client/My_Repository_ID/g" /etc/leapp/files/repomap.json
```
Use the repository ID identified above as My_Repository_ID.

Running Leapp

Procedure

On Oracle Linux 7 only: Set the ENABLE_REPO_LIST environment variable:
```
# export ENABLE_REPO_LIST="--enablerepo=My_Repository_ID"
```
Use the repository ID of your orcharhino Client for Oracle Linux 8 repository as My_Repository_ID.
Perform Leapp pre-upgrade checks:
```
# leapp preupgrade $ENABLE_REPO_LIST
```
Note that the Leapp pre-upgrade check is expected to fail during the first run, but report issues and inhibit the upgrade. Examine the report in the /var/log/leapp/leapp-report.txt file, answer all questions using leapp answer, and manually resolve the other reported problems. If you encounter any additional issues, please have a look at the orcharhino Knowledge Base or contact the orcharhino support team.
On Red Hat Enterprise Linux 7 only: Remove a no longer required Kernel module:
```
# rmmod pata_acpi
```

Provide answers to the Leapp upgrade process:

# leapp answer --section remove_pam_pkcs11_module_check.confirm=True

Rerun the Leapp pre-upgrade checks:
```
# leapp preupgrade $ENABLE_REPO_LIST
```
If Leapp reports issues, please contact us.
On Oracle Linux 7 only: Ensure that your orcharhino Proxy does not run Oracle’s Unbreakable Enterprise Kernel during the Leapp upgrade. For more information, see Leapp Preupgrade fails on Oracle Linux 7 due to UEK in the ATIX Service Portal.
On Oracle Linux 7 only: Ensure uname26 is not installed:
```
# yum remove uname26
```
Perform the Leapp upgrade:
```
# leapp upgrade $ENABLE_REPO_LIST
```

Reboot your orcharhino Proxy:

# reboot

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

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: Succeeded.. If Leapp reports errors, please contact us.

On Alma Linux 8 only: Remove all no longer required repository files:

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

On Oracle Linux 8 only: Remove all no longer required repository files:

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

Remove all temporary repository file backups:
```
# rm /etc/yum.repos.d/*.original
```
Configure orcharhino Proxy:
```
# orcharhino-installer
```

Reindex the PostgreSQL database:

# cd /
# runuser -u postgres -- reindexdb -a

Update all packages on your orcharhino Proxy:
```
# dnf update
```

Empty the list of protected packages:

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

List remaining EL7-specific packages:

# rpm -qa | grep -e "\.el[67]" | grep -vE "^(gpg-pubkey|libmodulemd|katello-ca-consumer|subscription-manager)" | sort -u

Remove remaining EL7-specific packages:
```
# dnf remove My_Remaining_EL7_Packages
```
Install the orcharhino-proxy package:
```
# dnf install orcharhino-proxy
```
Optional: If you require SELinux to be in enforcing mode, perform the following steps:
1. Set SELinux=enforcing in /etc/selinux/config.
2. Reinstall required packages:
  # dnf reinstall foreman-selinux
3. Reconfigure orcharhino Proxy:
  # orcharhino-installer # touch /.autorelabel
Reboot your orcharhino Proxy:
```
# reboot
```
Verify all orcharhino Proxy services are running:
```
# systemctl status foreman-proxy.service
```
In the orcharhino management UI, navigate to Infrastructure > Smart Proxies and select your orcharhino Proxy. Ensure the table specifies No Failed Features.