Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2168504

Summary: [Azure]crashkernel=auto after leapp upgrade from 8.8 to 9.2
Product: Red Hat Enterprise Linux 9 Reporter: Yuxin Sun <yuxisun>
Component: kexec-toolsAssignee: Coiby <coxu>
Status: CLOSED ERRATA QA Contact: Yuxin Sun <yuxisun>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.2CC: coxu, litian, ltao, ruyang, xuli, xxiong, yacao
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: coxu: needinfo-
pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kexec-tools-2.0.25-12.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:14:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yuxin Sun 2023-02-09 09:01:21 UTC
Description of problem:
After leapp upgrade from 8.8 to 9.2 on Azure, crashkernel is still auto.

Version-Release number of selected components (if applicable):
RHEL version: RHEL-8.8.0-20230208.29 -> RHEL-9.2.0-20230201.12
kexec-tools-2.0.25-5.el8.x86_64.rpm
Leapp:
leapp-0.15.0-100.20230127162719955417.master.20.gd715ab0.el8.noarch
leapp-upgrade-el8toel9-deps-0.17.0-100.20230207100135858965.master.84.g8a1fec7.el8.noarch
leapp-upgrade-el8toel9-0.17.0-100.20230207100135858965.master.84.g8a1fec7.el8.noarch
leapp-deps-0.15.0-100.20230127162719955417.master.20.gd715ab0.el8.noarch
leapp-rhui-azure-1.0.0-1.el8.noarch
python3-leapp-0.15.0-100.20230127162719955417.master.20.gd715ab0.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1. Prepare a RHEL-8.8 VM on Azure
2. Leapp upgrade to 9.2:
- Setup oamg repo and install leapp-upgrade-el8toel9
- Download leapp files, prepare leapp_upgrade_repositories.repo and put in /etc/leapp/files
- Install leapp-rhui-azure-1.0.0-1.el8.noarch
- LEAPP_UNSUPPORTED=1 LEAPP_DEVEL_DATABASE_SYNC_OFF=1 LEAPP_DEVEL_TARGET_RELEASE=9.2 leapp upgrade --debug --no-rhsm --reboot

Actual results:
After upgrade, check /proc/cmdline:
...crashkernel=auto
# kdumpctl status
kdump: Kdump is not operational

Console logs after upgrade and reboot:
[  290.404896] upgrade[1530]:   Running scriptlet: kexec-tools-2.0.25-11.el9.x86_64                 1271/1271
[  290.408510] upgrade[1530]: kdump: Updated crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M for kernel=/boot/vmlinuz-4.18.0-457.el8.x86_64. Please reboot the system for the change to take effect.

It only updates the RHEL-8 kernel but not RHEL-9.
# grubby --info=ALL
index=0
kernel="/boot/vmlinuz-5.14.0-249.el9.x86_64"
args="ro loglevel=3 crashkernel=auto console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 rd.plymouth=0 plymouth.enable=0 rd.plymouth=0 plymouth.enable=0 $tuned_params"
root="/dev/mapper/rootvg-rootlv"
initrd="/boot/initramfs-5.14.0-249.el9.x86_64.img $tuned_initrd"
title="Red Hat Enterprise Linux (5.14.0-249.el9.x86_64) 9.2 (Plow)"
id="80edae9d425c43a88ec5de74c2fbf312-5.14.0-249.el9.x86_64"
index=1
kernel="/boot/vmlinuz-4.18.0-457.el8.x86_64"
args="ro loglevel=3 console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 $tuned_params crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M"
root="/dev/mapper/rootvg-rootlv"
initrd="/boot/initramfs-4.18.0-457.el8.x86_64.img $tuned_initrd"
title="Red Hat Enterprise Linux (4.18.0-457.el8.x86_64) 8.8 (Ootpa)"
id="80edae9d425c43a88ec5de74c2fbf312-4.18.0-457.el8.x86_64"

Expected results:
crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M after upgrade

Additional info:
No such issue in Hyper-V and AWS.

Comment 2 Coiby 2023-02-13 02:18:32 UTC
Hi Yuxin,

I'm a bit confused that this issue doesn't happen to Hyper-V. Could you paste a console log for Hyper-V? Thanks!

Comment 21 errata-xmlrpc 2023-05-09 08:14:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (kexec-tools bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2463