Control Web Panel

WebPanel => CentOS-WebPanel Bugs => Topic started by: Wonder on November 19, 2026, 07:22:25 AM

Title: CWP 1.30.24 – Default kernel not restored after update
Post by: Wonder on November 19, 2026, 07:22:25 AM
Hi,

I noticed an issue on one of my AlmaLinux 10.3 servers running CWP 1.30.24 (LTS).

I saw in the changelog that version 1.30.24 fixes a problem where CWP was installing and setting Secure Kernel as the default, even on servers that had never enabled it.

Even after updating to CWP 1.30.24, the default kernel was still pointing to the CWP one instead of the standard AlmaLinux kernel.

This is what I was getting:

# grubby --default-kernel
/boot/vmlinuz-6.12.0-211.69.1.el10_2.cwpsec.x86_64

And GRUB was still pointing to the same kernel:

# grub2-editenv list
saved_entry=99c9e38024cc4287a0d3afea78a62e93-6.12.0-211.69.1.el10_2.cwpsec.x86_64

The latest AlmaLinux 10.3 kernel was already installed, so I changed the default manually:

grubby --set-default /boot/vmlinuz-6.12.0-264.16.1.el10_3.x86_64

After rebooting, everything seems to be working fine:

# uname -r
6.12.0-264.16.1.el10_3.x86_64

# grubby --default-kernel
/boot/vmlinuz-6.12.0-264.16.1.el10_3.x86_64

I also have another AlmaLinux 10.3 server running CWP Edge 2.0.18. That server has the `cwpsec` kernel installed too, but it's running the standard AlmaLinux kernel without any issues.

I haven't seen this problem on my AlmaLinux 8 server running CWP LTS either.

Just wanted to report this in case the automatic fix in 1.30.24 isn't working on all servers.

Is changing the default kernel with `grubby` enough, or does the CWP fix also make other changes?

Thanks!
Title: Re: CWP 1.30.24 – Default kernel not restored after update
Post by: 6Sense on November 19, 2026, 08:02:34 AM
CWP support gave me these instructions

1. stop CWP from re-pinning or reinstalling the Secure Kernel
mkdir -p /etc/cwpsecure
printf 'selfheal=0\nguard=0\nauto_install=0\n' >> /etc/cwpsecure/kernel_update.conf

2. list installed kernels and pick the newest stock one (without "cwpsec")
grubby --info=ALL | grep ^kernel

3. set it as default (replace with the exact path from step 2), check, then reboot
grubby --set-default /boot/vmlinuz-4.18.0-553.XX.X.el8_10.x86_64
grubby --default-kernel
reboot

After the reboot, "uname -r" should show the stock kernel. Optionally you can then remove the Secure Kernel packages: dnf remove 'kernel*cwpsec*'
Title: Re: CWP 1.30.24 – Default kernel not restored after update
Post by: Wonder on November 19, 2026, 08:17:16 AM
Thanks for sharing the instructions!

I've already switched back to the stock AlmaLinux kernel using `grubby --set-default`, and everything is working fine after the reboot.

I also checked `/etc/cwpsecure/`. The `kernel_update.conf` file doesn't exist, but I found a `kernel_update.state` file containing `sk_ever_installed`.

For now, I'll leave the Secure Kernel packages installed and keep an eye on future CWP updates to see if the default kernel changes again.

Thanks again for your help!