Kernel Elevate blocker Centos 7 to Almalinux

Humphrey Mutai

• September 07, 2024 09:52
• Edited

Hello,

When running the elevate script, the below blocker appears:

Newest installed kernel not in use

  To ensure a stable upgrade, the machine needs to be booted into the latest installed kernel.

  Possible resolution: Boot into the most up-to-date kernel installed on the machine before running Leapp again.

Any suggestion on the best way to sort this and upgrade.

 

Thanks.

• 

  ffeingol

  • September 07, 2024 14:09

  Reboot.  Seems like a kernel got installed, but you never rebooted.

  0
• 

  Humphrey Mutai

  • September 07, 2024 14:49

  Thanks for responding. I've rebooted severally, however I still seem to be booted into a different kernel from the system default.

  0
• 

  Humphrey Mutai

  • September 07, 2024 15:20

  The below is the output from running elevate --check:

  2024-09-07 15:12:17 [INFO] Successfully verified signature for cpanel (key types: release).

  * 2024-09-07 15:12:17 [INFO] Running: /usr/bin/yum list extras

  * 2024-09-07 15:12:17 [INFO] 

  * 2024-09-07 15:12:23 [ERROR] 1 package(s) installed from unsupported YUM repo 'elrepo' from /etc/yum.repos.d/elrepo.repo

  * 2024-09-07 15:12:28 [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.

  * 2024-09-07 15:12:28 [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VAS4PvlJmk/ea_profile.json

  * 2024-09-07 15:12:28 [INFO] Backed up EA4 profile to /tmp/VAS4PvlJmk/ea_profile.json

  * 2024-09-07 15:12:34 [WARN] *** Elevation Blocker detected: ***

    The running kernel version (3.10.0-1160.45.1.el7.x86_64) does not match that of

    the default boot entry (3.10.0-1160.119.1.el7.tuxcare.els2.x86_64). This could be due to the kernel

    being changed by an update, meaning that a reboot should resolve this.

    However, this also could indicate that the system does not have control

    over which kernel and early boot environment (initrd) is used upon

    reboot, which is required to upgrade the operating system with this

    script.

    

    If this message remains after a reboot, your server may have been

    configured to boot into a particular kernel directly rather than to an

    instance of the GRUB2 boot loader. This often happens to virtualized

    servers, but physical servers also can have this problem under certain

    configurations. Your provider may have a solution to allow booting into

    GRUB2; contact them for further information.

  0
• 

  Andrew

  • September 08, 2024 20:07

  If you have KVM access you can manual select the newest kernel during boot otherwise check your boot entries and see if the most up to date kernel is the first there.

  Andrew N. - cPanel Plesk VMWare Certified Professional
  Do you need immediate assistance? 20 minutes response time!* Open a ticket
  EmergencySupport - Professional Server Management and One-time Services

  0

Please sign in to leave a comment.