Skip to main content

Upgrading Issue for RHEL 7 to 8 With Leapp

Overview

The Leapp utility is a framework for updating and upgrading operating systems as well as applications. The operations of this utility consist of two phases 1. the preupgrade Phase – that chack the upgrade possibilities and 2. the actual upgrade phase – that map packages between previous and current versions of the software packages.

Issue – 01:

After running ‘sudo leapp preupgrade‘ sometimes you find the below issue in ‘/var/log/leapp/leapp-report.txt‘.

Detail:

Risk Factor: high (inhibitor)
Title: Leapp detected loaded kernel drivers which have been removed in RHEL 8. Upgrade cannot proceed.
Summary: Support for the following RHEL 7 device drivers has been removed in RHEL 8:
– pata_acpi

Key: f08a07da902958defa4f5c2699fae9ec2eb67c5b

Remediation:

1. Disable detected kernel drivers in order to proceed with the upgrade process using the rmmod or modprobe -r.

rmmod – Simple program to remove a module from the Linux Kernel
modprobe – Add and remove modules from the Linux Kernel
# sudo rmmod pata_acpi

or

# sudo modprobe -r pata_acpi

Run ‘sudo leapp preupgrade‘ and again check the issue in ‘/var/log/leapp/leapp-report.txt‘.

Issue – 02:

Aftur running ‘sudo leapp preupgrade‘ sometimes you find the below issue in ‘/var/log/leapp/leapp-report.txt‘.

Detail:

Risk Factor: high (inhibitor)
Title: Detected loaded kernel drivers which have been removed in RHEL 8. Upgrade cannot proceed.
Summary: Support for the following RHEL 7 device drivers has been removed in RHEL 8:
mptbase
mptscsih
mptspi

Remediation:

1. Backup currently used kernel image file that is known as initramfs

# sudo cp /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak

2. And then build a generic initramfs containing all drivers

# sudo dracut -N -f

3. Shutdown the system

4. On the VMWare Hypervisor side
Login your VM Server such as ESXi and then select your VM machine then go to it’s Edit setting option. Change “SCSI Controller” type to “VMware Paravirtual” if not. After that save change and power on your machine.
5. Once booted run following command

# sudo dracut -f --regenerate-all

Run ‘sudo leapp preupgrade‘ and again check the issue in ‘/var/log/leapp/leapp-report.txt‘.

If your kernel panicked or tempered somehow you can follow this Remediation process to get rid of it.

Issue – 03:

After running ‘sudo leapp preupgrade‘ sometimes you find the below issue in ‘/var/log/leapp/leapp-report.txt‘.

Detail:

Risk Factor: high (inhibitor)
Title: Leapp detected loaded kernel drivers which have been removed in RHEL 8. Upgrade cannot proceed.
Summary: Support for the following RHEL 7 device drivers has been removed in RHEL 8:
– pata_acpi

Key: f08a07da902958defa4f5c2699fae9ec2eb67c5b

Note: pata, Parallel ATA (PATA), originally AT Attachment, is an Internal storage device connector and ACPI stands for Advanced Configuration and Power Interface

Remediation:

To resolve the above issue, we need to disable ACPI completely in grub2.

Disable ACPI completely in grub


If ‘/sys/firmware/efi‘ exists means system uses UEFI otherwise system uses BIOS.

1. For an MBR (BIOS-based) system

1.1. Backup ‘/etc/default/grub‘ and ‘/boot/grub2/grub.cfg‘ files

# sudo cp -v /etc/default/grub /etc/default/grub.bak
# sudo cp -v /boot/grub2/grub.cfg /boot/grub2/grub.cfg.bak


And disable ACPI in ‘/etc/default/grub‘ file by append ‘noacpi acpi=off‘ to the GRUB_CMDLINE_LINUX option.

# sudo vi /etc/default/grub


GRUB_CMDLINE_LINUX=”crashkernel=auto rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet noacpi acpi=off”

1.2. Now generate a new grub.cfg file and reboot the system.

# sudo grub2-mkconfig -o /boot/grub2/grub.cfg
# sudo systemctl reboot


2. For a GPT (UEFI-based) system

2.1. Backup ‘/etc/default/grub‘ and ‘/boot/efi/EFI/redhat/grub.cfg‘ files

# sudo cp -v /etc/default/grub /etc/default/grub.bak
# sudo cp -v /boot/efi/EFI/redhat/grub.cfg /boot/efi/EFI/redhat/grub.cfg.bak


And disable ACPI in ‘/etc/default/grub‘ file by append ‘noacpi acpi=off‘ to the GRUB_CMDLINE_LINUX option.
# sudo vi /etc/default/grub

GRUB_CMDLINE_LINUX=”crashkernel=auto rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet noacpi acpi=off”

2.2. Now generate a new grub.cfg file and reboot the system.

# sudo grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
# sudo systemctl reboot

Run ‘sudo leapp preupgrade‘ and again check the issue in ‘/var/log/leapp/leapp-report.txt‘.

Conclusion

This tutorial helps you How to upgrade your existing Oracle Linux 7 system to 8. If have any queries please comment to us. follow the link to Upgrading Redhat Linux 7 to 8 With Leapp.

References

In this tutorial, I follow the official docs as reference Performing Systems Upgrade With Leapp (Oracle Linux 8).

Comments

Popular posts from this blog

ORA-00800: soft external error arguments

The problem as stated: After upgrading the Oracle Database from 12c to 19c the following error generated in the alert log file. Actual Oracle Error Code: ORA-00800 After Upgrading from 12c to 19c ORA-00800: soft external error, arguments occured Oracle Database Enterprise 19c fails to start with error: ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM] Why does Insights prevent Oracle grid services from starting How to configure the User slice to allow Real-Time Scheduling for user processes In Alert Log: Errors in file /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/trace/psbcdb_vktm_3529.trc (incident=1200048) (PDBNAME=CDB$ROOT): ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM], [Check traces and OS configuration], [Check Oracle document and MOS notes], [] Incident details in: /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/incident/incdir_1200048/psbcdb_vktm_3529_i1200048.trc 2023-10-30T10:04:53.536165+06:00 Error attempting to elev...

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. 1.0. error message: Error Message: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. Pass in a valid hostname and port number for the OMS to successfully deploy the agent. 1.1. deploy log: Log: /opt/gc_inst/em/EMGC_OMS1/sysman/agentpush/2023-11-07_16-09-23-PM/applogs/dblivesrv_deploy.log Execution of command cd /opt/agent/ADATMP_2023-11-07_16-09-23-PM;/opt/agent/ADATMP_2023-11-07_16-09-23-PM/agentDeploy.sh -ignorePrereqs ORACLE_HOSTNAME=dblivesrv AGENT_BASE_DIR=/opt/agent OMS_HOST=oemsrv.localdomain EM_UPLOAD_PORT=4903 AGENT_INSTANCE_HOME=/opt/agent/agent_inst b_doDiscovery=false START_AGENT=false b_forceInstCheck=true -force AGENT_PORT=3872 on host dblivesrv Failed 1.2. oms details: [oracle@oemsrv ~]$ $OMS_HOME/bin/emctl status oms -details Oracle Enterprise Manager Cloud Control 13c Release 5 Copyright (c) 1996, 2...