RHEL 8 Boots Older Kernel After Successful Update

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

uname -r shows an old kernel even after dnf update installed a newer one. Security and performance fixes remain inactive until the intended kernel boots.

Environment & Reproduction

Systems with multiple kernels, custom GRUB entries, or image-based provisioning frequently exhibit this. Rebooting after updates still returns previous kernel versions.

Root Cause Analysis

GRUB default entry points to an older index, or kernel-install hooks did not update bootloader state correctly. Manual edits in /etc/default/grub can also preserve legacy defaults.

Quick Triage

Compare installed kernels with rpm -q kernel and confirm boot default through grubby –default-kernel. Review recent boot logs using journalctl -b -1 for boot selection clues.

Step-by-Step Diagnosis

Inspect GRUB menu entries and BLS snippets under /boot/loader/entries, then map them to installed kernels. Validate EFI versus BIOS boot path consistency before applying fixes.

Solution – Primary Fix

Set the expected kernel with grubby –set-default, regenerate grub configuration if needed, and reboot. Validate with uname -r and grubby –default-kernel post-boot.

Solution – Alternative Approaches

Use kernel-install and BLS tooling for standardized lifecycle management, or pin a tested kernel temporarily during staged rollouts. Automation can enforce consistent default selection.

Verification & Acceptance Criteria

After reboot, running kernel matches the latest approved package, and boot logs show clean startup. No fallback to older entries should occur without explicit operator action.

Rollback Plan

Revert default to previously stable kernel using grubby and reboot if regressions appear. Keep at least two known-good kernels installed for controlled rollback.

Prevention & Hardening

Audit GRUB defaults during patching, monitor kernel drift in compliance checks, and avoid manual bootloader edits outside change management. Validate update hooks in golden images.

Automate patch management and compliance across your fleet with our DevOps services.

Related Errors & Cross-Refs

Similar symptoms appear with failed initramfs generation, disk space pressure in /boot, and accidental kernel package removal. Investigate these if default selection seems correct.

Related tutorial: View the step-by-step tutorial for rhel-8.

View all rhel-8 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

See Red Hat docs for kernel lifecycle, grubby usage, and boot loader specification behavior in RHEL 8.