modprobe: ERROR: could not insert 'kmodlve': Invalid argument / cloudlinux-default profile does not switch to -cgv1 after tuned-profiles-cloudlinux update

Issue

On CloudLinux 9 servers, after installing or updating tuned-profiles-cloudlinux, the active TuneD profile may remain cloudlinux-default instead of switching to cloudlinux-default-cgv1 automatically.

As a result, the server may boot with the system default cgroup mode for the OS. On CloudLinux 9, this means cgroups v2, while the CloudLinux kernel module still expects cgroups v1.

• Customers may also ask whether cloudlinux-default now implies cgroups v2, because previously there was no split between the old default profile and the new -cgv1 / -cgv2 variants.

# stat -fc %T /sys/fs/cgroup/
cgroup2fs

• Failure to load kmodlve CL kernel module:

# modprobe kmodlve 
modprobe: ERROR: could not insert 'kmodlve': Invalid argument 

• /var/log/messages contains these errors:

kernel: kmodlve: loading out-of-tree module taints kernel.
kernel: kmodlve: cgroups v2 not supported
lve-kmod.sh[2401]: modprobe: ERROR: could not insert 'kmodlve': Invalid argument
lve-kmod.sh[2353]: LVE module is missing

Environment

• CloudLinux OS 9

• Component: Kernel / TuneD profiles

• Package: tuned-profiles-cloudlinux

• Affected observed version: 0.2-11.el9

• Example active profile: cloudlinux-default

• Related profile: cloudlinux-default-cgv1

Solution

Our team has released a fix for cgroups v2 not supported. Update tuned-profiles-cloudlinux to a fixed version.
 

The fix was released in:

• CL8 / CL9: tuned-profiles-cloudlinux-0.2-13

• CL10: tuned-profiles-cloudlinux-0.3-5

• Ubuntu 22: tuned-profiles-cloudlinux-0.2-9

Cause

Starting from tuned-profiles-cloudlinux 0.2-11, the main TuneD profiles were split into separate variants with -cgv1 and -cgv2 suffixes.

The cloudlinux-default profile is no longer intended for direct use as the cgroup-aware default profile. It contains only common tunings and does not include the cgroup-specific boot parameters. On CloudLinux 9, using cloudlinux-default can therefore leave the system booting with the OS default cgroups v2 behaviour.

In the reported case, developers suspected a race condition that prevented the package installation from automatically switching the system to cloudlinux-default-cgv1. This behaviour was tracked internally under CLKRN-2076 and later fixed in newer package versions.