CloudLinux ELevate Project
The ELevate project is an initiative to support migrations between major versions of RHEL derivatives.
The CloudLinux ELevate variant, built on top of the AlmaLinux ELevate project, aims to provide a streamlined method of upgrading CloudLinux 7.X systems to CloudLinux 8.X in place.
The Leapp utility is the main tool used to perform the upgrade.
We strongly recommend all the ELevate operations to be performed by a system administrator or DevOps with the required expertise level: advanced.
The CloudLinux ELevate project
The CloudLinux ELevate project is currently released to stable. Migrating from CloudLinux 7.X to CloudLinux 8.X on no‑panel systems and cPanel is supported.
Latest Updates
CloudLinux ELevate: Stable version is now released. Simplified transitioning from CloudLinux 7 to 8. Learn more
According to the Support policy, the Support team is not responsible to provide support for any third-party utilities which might not function after the upgrade. For example, web servers, DNS servers, mail servers, database servers, and other utilities that do not belong to the CloudLinux product line.
- This might cause your utilities and services to stop working after the update.
- This might cause your utilities and services to stop working on the post-upgrade machine.
CloudLinux does not provide support related to integrating third-party repositories or packages into the upgrade process. However, you can add the aforementioned components to the Leapp database yourself. Please check the Third-party integration section in the linked README for instructions on integrating external repositories.
While the ELevate project and its surrounding ecosystem are mature, support for CloudLinux has been introduced quite recently, and as such, hasn’t been thoroughly tested and verified yet.
In particular, systems with configurations and packages that substantially differ from a typical CloudLinux OS 7 installation could encounter issues not seen before.
A full system upgrade is an inherently invasive procedure. In some cases, due to different system configurations, package errors, or even power failures, you may encounter issues during the upgrade process that can’t be automatically recovered from.
Said issues may be severe, up to and including rendering the system completely inaccessible.
To that end, it’s highly recommended never to run ELevate on a system without a backup ready.
Ideally, perform a trial run in a disposable environment, like a VM or a sandbox, to verify that migration functions as expected before you attempt to migrate a system.
The ELevate project only supports a subset of package repositories it’s aware of – that is, package repositories that are included in its configuration files.
Packages from repositories Leapp is unaware of will not be upgraded.
It’s possible to add missing repositories and packages to ELevate yourself if you’re so inclined. Please check the Contribution section for more information on how to do so.
One of the major steps of the upgrade process involves rebooting into a special initramfs environment, from which your system’s software will be upgraded. During that period of time, the system will be mostly non-functional and inaccessible.
This stage may take up to an hour, so schedule the upgrade accordingly.
During the preparation stages – that is, when the upgrade process is first initiated and before the system is rebooted – the system’s services will function normally.
CloudLinux 7 no panel/custom panel and cPanel upgrade scenarios behave somewhat differently during the preparation stage. The cPanel scenario will disable the site functionality from this stage up until completion, while the no-panel/custom panel scenario will not.
If the machine remains unresponsive for more than 2 hours after rebooting, assume the upgrade process failed during the post-reboot phase.
Depending on the web panel you have installed on your system, the upgrade process will require different steps.
At the moment, ELevate migration from CloudLinux 7 to CloudLinux 8 is supported on the following:
- no panel/custom panel systems;
- cPanel systems.
I have a CloudLinux 7 system with no web panel/a custom web panel installed, how do I upgrade to CloudLinux 8?
In such a case, you can upgrade through the Leapp tool directly.
Please refer to the CloudLinux 7 with no panel/custom panel ELevate Scenario for step-by-step instructions.
I have a CloudLinux 7 system with cPanel installed, how do I upgrade to CloudLinux 8?
With cPanel present on the machine, you should run the upgrade process through the elevate-cpanel tool.
Please refer to the CloudLinux 7 with cPanel ELevate Scenario for step-by-step instructions.
I have a CloudLinux 7 system with DirectAdmin/Plesk/another panel installed, how do I upgrade to CloudLinux 8?
Unfortunately, CloudLinux ELevate doesn’t support these system configurations yet.
Instead, you can create a new machine with CloudLinux 8 and migrate your system’s license and configuration to it.
Please refer to the following documentation links for instructions on how to do so:
When filing an issue, include:
- Steps to reproduce the issue
- All files in the
/var/log/leapp>
/var/lib/leapp/leapp.db
- journalctl
- Also, you can provide other helpful materials (e.g. storage info)
For your convenience you can pack all logs with the following command:
# tar -czf leapp-logs.tgz /var/log/leapp /var/lib/leapp/leapp.db
Then you may attach only the leapp-logs.tgz
file.
Before gathering data, if possible, re-run the leapp command that encountered an issue with the --debug
flag, e.g.: leapp upgrade --debug
.
/var/log/leapp/leapp-report.txt
/var/log/leapp/leapp-report.json
/var/log/leapp/leapp-upgrade.log
Therefore, although IPMI/VNC access is not strictly necessary, it’s recommended, since it’ll be difficult to monitor the main upgrade transaction otherwise.