This article contains instructions for updating the operating system (OS) on the platform server and cluster nodes from AlmaLinux 9 to AlmaLinux 10.
If you need to change the OS from AlmaLinux 8 to AlmaLinux 10, update the OS to AlmaLinux 9 according to the article Migrating from AlmaLinux 8 to AlmaLinux 9, then follow the instructions from this article.
Update procedure
Platform server
To update the OS:
- Check the compatibility of the hardware with new AlmaLinux version. To do this, boot the AlmaLinux OS in Live Media mode.
- Create a backup of the platform on external storage. For more information, see Creating platform backups.
- Follow the instructions in the OS Update section.
The platform will be unavailable during the OS change process.
Cluster node
There are two options for updating the OS:
- with virtual machines (VMs) migrated to another node — the recommended method;
- without transferring VMs — successful update is not guaranteed, use this method at your own risk.
To update the OS with VMs migration:
- Migrate VMs to another node. For more information, see Migration of virtual machines.
- Delete the cluster node.
- Erase server disks and install new AlmaLinux version on it.
- Connect the node to the cluster.
- MIgrate VMs back to the node.
To update the OS without VMs migration:
- Check the compatibility of the hardware with new AlmaLinux version. To do this, boot the AlmaLinux OS in Live Media mode.
- Follow the instructions in the OS Update section. VMs on the cluster node will be unavailable during the OS change process.
OS update
- Connect to the server via SSH. For more information about connecting via SSH, see Workstation setup.
- Update the software:
yum update - Reboot the server:
reboot - Connect to the server via SSH again.
- Install the ELevate software:
yum install -y http://repo.almalinux.org/elevate/elevate-release-latest-el$(rpm --eval %rhel).noarch.rpm - Instal the Leapp framework:
yum install -y leapp-upgrade leapp-data-almalinux - Remove the kernel module for iSCSI adapters:
rmmod qla4xxx - Change the format of the network connection configuration to a format supported by Network Manager:
nmcli con migrate - Delete the Ceph repository configuration file:
rm /etc/yum.repos.d/ceph.repo -
Check if the system is ready for the OS change:
leapp preupgradeExamine the output of the command and the report file /var/log/leapp/leapp-report.txt. They contain information about possible problems when changing OS.
-
Start the OS change:
leapp upgrade -
Reboot the server:
reboot- The server may reboot longer than usual due to the OS change.
- Ensure that the AlmaLinux 10 kernel is selected in the boot loader menu.
- Connect to the server via SSH again.
-
Check the OS version:
cat /etc/os-release - Remove the AlmaLinux 9 packages:
- Get the package list:
rpm -qa | grep el9 - Remove each package from the list with the command:
dnf remove <имя_пакета>
- Get the package list:
If the frr service was used on the cluster node
- Connect to the cluster node via SSH. For more information about connecting via SSH, see Workstation setup.
- In the file /etc/yum.repos.d/frr-stable.repo, replace links of the form to
https://rpm.frrouting.org/repo/el9https://rpm.frrouting.org/repo/el10 - Update the software:
dnf update
If you did not migrate VMs before migration
- Connect to the cluster node via SSH. For more information about connecting via SSH, see Workstation setup.
- Change the XML configurations for all VMs:
for vm in $(virsh list --all | awk 'NR>2 {print $2}') do EDITOR="sed -i -e s/pc-i440fx-rhel7.6.0/pc-i440fx-rhel10.0.0/ -e s/cirrus/virtio/" virsh edit $vm done - Start the VMs:
for vm in $(virsh list --all --autostart | awk 'NR>2{print $2}'); do virsh start $vm; done
En
Es