Preconversion check error / No Red Hat signed kernel is installed

[Wanerys]

Hi,

I try to update one server from Centos 7.9 to Almalinux 8.
I use: https://support.plesk.com/hc/en-us/...f-a-Plesk-server-from-CentOS-7-to-AlmaLinux-8

I have this error during the pre check:

Required pre-conversion condition 'checking if the Red Hat kernel is installed' not met:
No Red Hat signed kernel is installed.
To proceed with the conversion, install a kernel by running:
- 'yum install kernel kernel-tools kernel-tools-libs'
After installing the kernel fix the grub configuration by calling:
- `grub2-set-default 'CentOS Linux (newly_installed_kernel_version) 7 (Core)'`
- `grub2-mkconfig -o /boot/grub2/grub.cfg`
- `reboot`

Is it safe to do this?
The server is working fine. It won't have any impact to modify the grub? There is currently no boot problem.

Actually i have:

# uname -r
4.9.185-xxxx-std-ipv6-64
# cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)

If I have to do the installation, what version should I put in:
grub2-set-default 'CentOS Linux (newly_installed_kernel_version) 7 (Core)'

If I start as suggested

#yum install kernel kernel-tools kernel-tools-libs

I have:

Installation :
kernel x86_64 3.10.0-1160.119.1.el7.tuxcare.els12 centos7els-rollout-2 52 M
kernel-tools x86_64 3.10.0-1160.119.1.el7.tuxcare.els12 centos7els-rollout-2 8.2 M
kernel-tools-libs x86_64 3.10.0-1160.119.1.el7.tuxcare.els12 centos7els-rollout-2 8.1 M
Installation pour dépendances :
grubby x86_64 8.28-26.el7 base 71 k

Thank you for your help.
Erwan

[SandakovMM]

Hello @Wanerys,

Is it safe to do this?

It is safe as long as you keep the currently installed kernel, so you can revert to it if needed
Unfortunately, we cannot carry out the conversion process with non-standard kernels. This is a requirement of the elevate utility we use for conversion

If I have to do the installation, what version should I put in:

The kernel version is 3.10.0-1160.119.1.el7.x86_64. I believe, you should be able to find the menuentry section for it in the /boot/grub2/grub.cfg file. On my test instance, it appears like this:

menuentry 'CentOS Linux (3.10.0-1160.119.1.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-1160.45.1.el7.x86_64-advanced-44a6a613-4e21-478b-a909-ab653c9d39df' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod xfs
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1'  44a6a613-4e21-478b-a909-ab653c9d39df
	else
	  search --no-floppy --fs-uuid --set=root 44a6a613-4e21-478b-a909-ab653c9d39df
	fi
	linux16 /boot/vmlinuz-3.10.0-1160.119.1.el7.x86_64 root=UUID=44a6a613-4e21-478b-a909-ab653c9d39df ro console=tty0 console=ttyS0,115200n8 crashkernel=auto net.ifnames=0 console=ttyS0 LANG=en_US.UTF-8
	initrd16 /boot/initramfs-3.10.0-1160.119.1.el7.x86_64.img
}

[Wanerys]

Hello @SandakovMM,

Thank you for your help.

It is safe as long as you keep the currently installed kernel, so you can revert to it if needed
Unfortunately, we cannot carry out the conversion process with non-standard kernels. This is a requirement of the elevate utility we use for conversion

So we can't use the conversion process... :(

menuentry 'CentOS Linux (4.9.185-xxxx-std-ipv6-64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.9.185-xxxx-std-ipv6-64-advanced-054226ad-e249-4af8-bc88-f01208349e05' {

Have you had any experience with Almalinux standard process? Is Plesk at risk of damage?
https://wiki.almalinux.org/elevate/ELevating-CentOS7-to-AlmaLinux-9.html#upgrade-centos-7-to-almalinux-8

[SandakovMM]

Have you had any experience with Almalinux standard process? Is Plesk at risk of damage?

Actually, centos2alma is based on the same process. We only add a few extra steps to ensure Plesk functions properly after conversion.

The requirement for having a kernel signed by RHEL comes specifically from AlmaLinux Elevate (though I believe it's more related to the leapp framework it relies on). Therefore, I think leapp might prevent the conversion.

However, you can test this by executing leapp preupgrade (centos2alma likely already installed leapp).
If the preupgrade is successful, you can go ahead with the conversion. But I advise against proceeding with leapp upgrade as it doesn't provide any extra measures specifically for Plesk. I would appreciate it if you could send me a feedback archive instead (you can generate one using centos2alma -f), so I can confirm whether our pre-checker functions the same way as leapp’s.