How to do inplace upgrade of RHEL 7 to RHEL8 and DLP 15.x to 16.0.x

Products

Data Loss Prevention

Issue/Introduction

Upgrade rhel 7 and DLP 15.8 to rhel 8 and DLP 16.x

Environment

RHEL 7

DLP 15.8, 16.0.x

Cause

rhel 7 is no longer supported in 16.x going forward. This process will allow in place upgrades to be able to upgrade DLP.

Resolution

DLP 16.x does not support rhel 7 past 16.0 GA. Customers will need to upgrade RHEL before they upgrade DLP.

In DLP 15.8, support for rhel 7 and rhel8 exists.

The order of operations are as follows:

Do an in-place upgrade of rhel 7 to rhel8.10
Do a migration of 15.8 to 16.x
Do an in-place upgrade for rhel 8 to 9.4 if required
Do a final migration of 16.x to 16.1

NOTE: connection to the physical console is recommended for this process. Running this from SSH connection will loose connection once the upgrade starts.

Preparing RHEL 7 for upgrade

Enable repositories so can we have the correct upgrade utilities

subscription-manager repos --enable rhel-7-server-rpms

Enable the extras repository to install leaap utility to run the upgrade.

subscription-manager repos --enable rhel-7-server-extras-rpms

Next, set the redhat subscription manger to use the latest rhel 7 content

subscription-manager release –unset

Next, install the leaap utility

yum install leapp-upgrade

Make sure rhel7 to updated and reboot

Yum update && reboot

Generate the preupgrade report.

Leaap preupgrade

Review the upgrade report in /var/log/leaap/leaap-report.txt

Any issues tagged as inhibitors or high should be addressed.

Examine the report in the /var/log/leapp/leapp-report.txt file and manually resolve all the reported problems. Some reported problems contain remediation suggestions. Inhibitor problems prevent you from upgrading until you have resolved them. For more information on the different problems that can appear in the report, see the pre-upgrade steps in the Red Hat Knowledgebase solution How do I upgrade from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8?

The report contains the following risk factor levels:

High

Very likely to result in a deteriorated system state.

Medium

Can impact both the system and applications.

Low

Should not impact the system but can have an impact on applications.

Info

Informational with no expected impact to the system or applications.

DLP packages will be tagged as high priority to address. To address those import the signing key in the DLP platform download

Rpm –import rpm --import Symantec_DLP_RPM_Signing_Key.asc

To verify the DLP rpms

Cd to the directory where the DLP rpms are located
rpm -K *rpm

Once all inhibitors have been address (NOTE: inhibitors in the leaap report will block the upgrade from completing)

Performing the upgrade

On your RHEL 7 system, perform the pre-upgrade phase:

# leapp upgrade --target <target_os_version>

Replace <target_os_version> with the target OS version, for example 8.10. If no target OS version is defined, Leapp uses the default target OS version specified in the table 1.1 in Supported upgrade paths.

NOTE: the upgrade will require a couple reboots and it is recommended to connect to the physical console to finish the upgrade.

At the beginning of the upgrade process, Leapp performs the pre-upgrade phase described in Reviewing the pre-upgrade report.

If the system is upgradable, Leapp downloads necessary data and prepares an RPM transaction for the upgrade.

If your system does not meet the parameters for a reliable upgrade, Leapp terminates the upgrade process and provides a record describing the issue and a recommended solution in the /var/log/leapp/leapp-report.txt file. For more information, see Troubleshooting.

Manually reboot the system

reboot