OLVM : Leapp Upgrade from OLVM 4.3.10 to 4.4.x
(Doc ID 2900355.1)
Last updated on FEBRUARY 22, 2024
Applies to:
Linux OS - Version Oracle Linux 7.6 with Unbreakable Enterprise Kernel [4.14.35] and laterLinux x86-64
Goal
Outline the process of Leapp upgrade from OLVM 4.3.10 to 4.4.x
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
1.Introduction |
2. Known Limitations |
3. Requirements |
4. Before you begin |
5. Upgrade process overview |
5.1 Check the certificates expiration date |
5.2 Update current version of 4.3.10 to the latest version |
5.3 Stand-alone Engine and Self-Hosted-Engine |
5.4 KVM host |
5.5 Final phase |
6. Prepare for the Upgrade : |
6.1 Check the certificates expiration date |
6.1.1 Engine server: |
6.1.2 KVM hosts: |
6.2 Update current version |
6.2.1 Update stand-alone Engine and Self- Hosted-Engine |
6.2.2 Upgrade the KVM hosts Gluster 6 to 8 |
6.2.3 Update KVM hosts |
7.Running the stand-alone engine and self-hosted-engine upgrade |
7.1 If running a Self-Hosted-Engine, put it into Global Maintenance mode |
7.2 Access the Engine server |
7.2.1 Connecting to the Engine using ssh |
7.2.2 Connecting to the Self-Hosted-Engine console |
7.3 Stopping the ovirt-engine service and backing up the database |
7.4 Install the leapp rpm package |
7.5 nbdkit rpm package upgrade exception |
7.6 Clear any version-locked rpm package list |
7.7 Proxy |
7.8 Preupgrade phase |
7.9 Possible fix examples |
7.9.1 ssh root login is not explicitly enabled |
7.9.2 Using old ethX network interfaces naming schema |
7.9.3 Editing the answer file |
7.10 Re-run the preupgrade phase |
7.11 Upgrade phase |
7.12 Tracking the single-user upgrade phase |
7.13 Remove any remaining Leapp packages from the exclude list |
7.14 Reinstalling the screen terminal emulator command |
7.15 Disabling the leapp repository |
7.16 Manually removing old orphan packages |
7.17 Proxy |
7.18 Configure the OLVM-4.4 repository |
7.19 OL8 repositories |
7.20 OS update |
7.21 Install the ovirt-engine rpm package |
7.22 Restore the ovirt-engine backup |
7.23 Run the engine-setup command |
7.24 Restart and enable the ovirt-engine.service |
7.25 Disable the Cluster Maintenance mode for the Self-Hosted-Engine |
8. Running the KVM host upgrade |
8.1 Put the KVM host into Maintenance mode |
8.2 Access the KVM host |
8.3 Mounted NFS shares |
8.4 Install the leapp rpm package |
8.5 nbdkit rpm package upgrade exception |
8.6 Clear any version-locked rpm package list |
8.7 Proxy |
8.8 Preupgrade phase |
8.9 Possible fix examples |
8.9.1 ssh root login is not explicitly enabled |
8.9.2 Using old ethX network interfaces naming schema |
8.9.3 Editing the answer file |
8.10 Re-run the preupgrade phase |
8.11 Upgrade phase |
8.12 Tracking the single-user upgrade phase |
8.13 Remove any remaining Leapp packages from the exclude list |
8.14 Reinstalling the screen terminal emulator command |
8.15 Disabling the leapp repository |
8.16 Manually removing old orphan packages |
8.17 Proxy |
8.18 Configure the OLVM-4.4 repository |
8.19 OL8 repositories |
8.20 Fix libvirtd-tls masked service |
8.21 OS update |
8.22 Install the ovirt-host rpm package |
8.23 NFS shares |
8.24 Activate the KVM host |
9. Upgrade Cluster Compatibility Version |
9.1 Upgrading the Cluster Compatibility Version |
9.2 Changing the Cluster Compatibility Version |
10. Upgrade the Virtual Machine Cluster Compatibility Version |
11. Upgrade the Data Center Compatibility Version |
11.1 Changing the Data Center Compatibility Version |