As technology evolves, so do operating systems. Upgrading your system is crucial to ensure you benefit from the latest features, improved security, and better performance. In this article, we’ll explore the importance of upgrading from RockyLinux 8 or AlmaLinux 8 to AlmaLinux 9 and provide a step-by-step guide to help you through the process.<\/p>\n\n\n\n
Before we initiate the upgrade process, it is important to backup your data to ensure that you have a copy in case anything goes wrong during the upgrade. Once you have backed up your data, you can proceed with the upgrade process with peace of mind.<\/p>\n\n\n\n
To successfully complete the upgrade, it is essential to have a fully updated system. Therefore, ensure that you install the latest updates and then restart your device.<\/p>\n\n\n\n
sudo yum update -y\nsudo reboot<\/code><\/pre>\n\n\n\nStep 2: Install upgrade package.<\/h4>\n\n\n\n
In order to access the latest version, it is necessary to install the upgrade package. Install the “elevate-release” package using the project repository and GPG key.<\/p>\n\n\n\n
sudo yum install -y http:\/\/repo.almalinux.org\/elevate\/elevate-release-latest-el$(rpm --eval %rhel).noarch.rpm<\/code><\/pre>\n\n\n\nStep 3: Installing leapp package and migrating data.<\/h4>\n\n\n\nsudo yum install -y leapp-upgrade leapp-data-almalinux<\/code><\/pre>\n\n\n\nThe above code is used to migrate data from AlmaLinux 8 to AlmaLinux 9. If you are looking to migrate from RockyLinux 8 to Almalinux 9 then replace “leapp-data-almalinux<\/code>” to “leapp-data-rocky<\/code>“. So, the command will be, sudo yum install -y leapp-upgrade leapp-data-rocky<\/code><\/p>\n\n\n\nStep 4: Run Pre-Upgrade Checks.<\/h4>\n\n\n\n
Run preupgrade checks to ensure that there are no compatibility issues or potential problems with the migration process. This step helps identify any system configurations or installed packages that might cause issues during the upgrade. Once the pre-upgrade checks have been completed successfully, you can proceed with confidence to the next step.<\/p>\n\n\n\n
sudo leapp preupgrade<\/code><\/pre>\n\n\n\nThe Leapp utility generates a unique file, located at \/var\/log\/leapp\/leapp-report.txt<\/em>, which provides insight into potential issues and offers suggested solutions. In certain configurations, Leapp generates \/var\/log\/leapp\/answerfile<\/em> with true\/false questions. Leapp utility requires answers to all these questions in order to proceed with the upgrade.<\/p>\n\n\n\nCommon issues during pre-upgarde check:<\/strong><\/p>\n\n\n\nIn certain cases, it generates the issue during pre-upgrade check due to permission of root login, security or due to some mods. You can review the \/var\/log\/leapp\/leapp-report.txt<\/em>\u00a0file for details. The most common issues can be resolved by applying the following fixes.<\/p>\n\n\n\nsudo rmmod pata_acpi\necho PermitRootLogin yes | sudo tee -a \/etc\/ssh\/sshd_config\nsudo leapp answer --section remove_pam_pkcs11_module_check.confirm=True<\/code><\/pre>\n\n\n\nEnsure that you enable root login if you are not using any other user login for your OS. It is often observed that server access is restricted after an upgrade because root access was not permitted to the system. Please run the command mentioned echo PermitRootLogin yes | sudo tee -a \/etc\/ssh\/sshd_config<\/code> to enable root login to the system.<\/p>\n\n\n\nBesides this, some of the most common fixes for RHEL8-based systems can be achieved by following commands:<\/p>\n\n\n\n
sudo sed -i \"s\/^AllowZoneDrifting=.*\/AllowZoneDrifting=no\/\" \/etc\/firewalld\/firewalld.conf\nsudo leapp answer --section check_vdo.no_vdo_devices=True<\/code><\/pre>\n\n\n\nStep 5: Run OS upgrade process<\/h4>\n\n\n\n
Make sure that all the preupgrade indicators are fixed, later you can proceed with the actual upgrade process.<\/p>\n\n\n\n
sudo leapp upgrade<\/code><\/pre>\n\n\n\nOnce the upgrade process is completed successfully, you can reboot the system.<\/p>\n\n\n\n
sudo reboot<\/code><\/pre>\n\n\n\nPlease allow some time for the system to reboot. This time the system may take a little longer to boot as it runs some update process during the first boot for completing the OS upgrade.<\/p>\n\n\n\n
Step 6: Post operating system upgrade (Optional)<\/h4>\n\n\n\n
After reboot, you can login to the system and check how the migration process went. Verify that the current OS is the one you need. Check logs and packages left from previous OS versions; consider removing them or updating them manually.<\/p>\n\n\n\n
cat \/etc\/redhat-release\ncat \/etc\/os-release\nrpm -qa | grep el7 # for 7 to 8 migration\nrpm -qa | grep el8 # for 8 to 9 migration\ncat \/var\/log\/leapp\/leapp-report.txt\ncat \/var\/log\/leapp\/leapp-upgrade.log<\/code><\/pre>\n\n\n\n