RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2083480 - [RHEL9] the kernel boot order can not modify with grubby
Summary: [RHEL9] the kernel boot order can not modify with grubby
Keywords:
Status: CLOSED DUPLICATE of bug 2015825
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: grubby
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bootloader engineering team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-10 08:12 UTC by guazhang@redhat.com
Modified: 2022-09-19 07:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-16 14:09:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
sosreport-storageqe-26-2022-05-10-hbpokzw.tar.xz (10.02 MB, text/plain)
2022-05-10 08:18 UTC, guazhang@redhat.com 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-121535 0 None None None 2022-05-10 08:30:27 UTC

Description guazhang@redhat.com 2022-05-10 08:12:32 UTC 
Description of problem:
install kernel to test server then modify the kernel boot order, the OS can not boot the new kernel after reboot. 

Version-Release number of selected component (if applicable):
5.14.0-85.el9.x86_64
grubby-8.40-55.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. install rhel9 
2. install new kernel which the version is lower than the default one
3. update the kernel boot order with grubby 


[root@storageqe-26 ~]# uname -a
Linux storageqe-26.sqe.lab.eng.bos.redhat.com 5.14.0-85.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Wed May 4 10:53:44 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux


install new kernel kernel-5.14.0-84.el9


[root@storageqe-26 ~]# grubby --info=ALL
index=0
kernel="/boot/vmlinuz-5.14.0-85.el9.x86_64"
args="ro loglevel=5 resume=/dev/mapper/rhel_storageqe--26-swap rd.lvm.lv=rhel_storageqe-26/root rd.lvm.lv=rhel_storageqe-26/swap console=ttyS1,115200 crashkernel=1G-4G:384M,4G-16G:512M,16G-64G:1G,64G-128G:2G,128G-:4G"
root="/dev/mapper/rhel_storageqe--26-root"
initrd="/boot/initramfs-5.14.0-85.el9.x86_64.img"
title="Red Hat Enterprise Linux (5.14.0-85.el9.x86_64) 9.1 (Plow)"
id="3cd05b1f48494611ba7d88a96183fe48-5.14.0-85.el9.x86_64"
index=1
kernel="/boot/vmlinuz-5.14.0-84.el9.x86_64"
args="ro loglevel=5 resume=/dev/mapper/rhel_storageqe--26-swap rd.lvm.lv=rhel_storageqe-26/root rd.lvm.lv=rhel_storageqe-26/swap console=ttyS1,115200 crashkernel=1G-4G:384M,4G-16G:512M,16G-64G:1G,64G-128G:2G,128G-:4G"
root="/dev/mapper/rhel_storageqe--26-root"
initrd="/boot/initramfs-5.14.0-84.el9.x86_64.img"
title="Red Hat Enterprise Linux (5.14.0-84.el9.x86_64) 9.1 (Plow)"
id="3cd05b1f48494611ba7d88a96183fe48-5.14.0-84.el9.x86_64"
index=2
kernel="/boot/vmlinuz-0-rescue-3cd05b1f48494611ba7d88a96183fe48"
args="ro loglevel=5 crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rhel_storageqe--26-swap rd.lvm.lv=rhel_storageqe-26/root rd.lvm.lv=rhel_storageqe-26/swap console=ttyS1,115200"
root="/dev/mapper/rhel_storageqe--26-root"
initrd="/boot/initramfs-0-rescue-3cd05b1f48494611ba7d88a96183fe48.img"
title="Red Hat Enterprise Linux (0-rescue-3cd05b1f48494611ba7d88a96183fe48) 9.1 (Plow)"
id="3cd05b1f48494611ba7d88a96183fe48-0-rescue"
[root@storageqe-26 ~]# 
[root@storageqe-26 ~]# grubby --set-default=/boot/vmlinuz-5.14.0-84.el9.x86_64 
The default is /boot/loader/entries/3cd05b1f48494611ba7d88a96183fe48-5.14.0-84.el9.x86_64.conf with index 1 and kernel /boot/vmlinuz-5.14.0-84.el9.x86_64
[root@storageqe-26 ~]# 
[root@storageqe-26 ~]# grubby --default-kernel
/boot/vmlinuz-5.14.0-84.el9.x86_64
[root@storageqe-26 ~]# rhts-reboot

after reboot, the OS will boot to kernel-5.14.0-85.el9.x86_64 and can not boot to kernel-5.14.0-84.el9.x86_64.

[root@storageqe-26 ~]# uname -a
Linux storageqe-26.sqe.lab.eng.bos.redhat.com 5.14.0-85.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Wed May 4 10:53:44 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
[root@storageqe-26 ~]# 


Actual results:
can not boot to new kernel even if have set the default kernel with grubby

Expected results:
boot to the default kernel which we set

Additional info:

for now, I just hit the bug with special test server 
https://beaker.engineering.redhat.com/view/storageqe-26.sqe.lab.eng.bos.redhat.com#details
Comment 2 guazhang@redhat.com 2022-05-10 08:18:37 UTC 
Created attachment 1878251 [details]
sosreport-storageqe-26-2022-05-10-hbpokzw.tar.xz
Comment 4 Marta Lewandowska 2022-09-16 11:53:59 UTC 
Hi guazhang and/or ChanghuiZhong, 
this is a UEFI machine, have you seen the same problem on Legacy BIOS?

https://bugzilla.redhat.com/show_bug.cgi?id=2101729
Comment 5 Marta Lewandowska 2022-09-16 14:09:38 UTC 

*** This bug has been marked as a duplicate of bug 2015825 ***
Comment 6 ChanghuiZhong 2022-09-19 06:31:55 UTC 
(In reply to Marta Lewandowska from comment #4)
> Hi guazhang and/or ChanghuiZhong, 
> this is a UEFI machine, have you seen the same problem on Legacy BIOS?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2101729

Hi，Marta

not seen this issue on Legacy BIOS machine，

Thanks，
Note You need to log in before you can comment on or make changes to this bug.