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 2104534 - Confusing warning despite success - "sed: can't read /etc/default/grub: No such file or directory" when running kdumpctl reset-crashkernel --kernel=ALL on s390x
Summary: Confusing warning despite success - "sed: can't read /etc/default/grub: No su...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kexec-tools
Version: 9.1
Hardware: s390x
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Coiby
QA Contact: Jie Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-06 14:51 UTC by smitterl
Modified: 2023-05-09 10:16 UTC (History)
6 users (show)

Fixed In Version: kexec-tools-2.0.25-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 08:14:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-127107 0 None None None 2022-07-06 15:04:42 UTC
Red Hat Product Errata RHBA-2023:2463 0 None None None 2023-05-09 08:14:55 UTC

Internal Links: 2104529 2104540

Description smitterl 2022-07-06 14:51:30 UTC 
Description of problem:
RHEL 9 documentation "11.1. Configuring kdump memory usage"[1] describes a way to reset the crashkernel size with kdumpctl. This command fails and customers on s390x seem to lack guidance about default values.

Version-Release number of selected component (if applicable):
kexec-tools-2.0.24-4.el9.s390x

How reproducible:
100%

Steps to Reproduce:
1. kdumpctl reset-crashkernel --kernel=ALL

Actual results:
sed: can't read /etc/default/grub: No such file or directory
sed: can't read /etc/default/grub: No such file or directory


Expected results:
The command succeeds; it updates the boot entries' crashkernel setting and runs 'zipl' to update the boot images.

Additional info:
[1]https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_monitoring_and_updating_the_kernel/configuring-kdump-on-the-command-line_managing-monitoring-and-updating-the-kernel

On s390x, per default BLS entries are used. I can successfully set a custom value via:

# grubby --update-kernel ALL --args "crashkernel=<CUSTOM-VALUE>”
# zipl

Note, on s390x, it's important to run 'zipl' after the grubby command (or usually after modifying kernel commandlines); if not the changes in the BLS entries won't be used when booting into the kernel; I verified this but I don't know the reason.

There's no grub support on s390x RHEL.

Customers can obtain the default crashkernel info via 'kdumpctl get-default-crashkernel' (verified on s390x, too).
Comment 2 Coiby 2022-07-08 01:05:44 UTC 
Thanks for reporting this bug! Despite the warnings of "sed: can't read /etc/default/grub: No such file or directory", kdumpctl has successfully  reset default crashkernel  value. Note on s390x, /etc/defaut/grub doesn't exist (bz21051180). I'll skip updating /etc/defaut/grub for 390x.
Comment 4 Coiby 2022-07-08 02:08:27 UTC 
(In reply to Coiby from comment #2)
> Thanks for reporting this bug! Despite the warnings of "sed: can't read
> /etc/default/grub: No such file or directory", kdumpctl has successfully 
> reset default crashkernel  value. Note on s390x, /etc/defaut/grub doesn't
> exist (bz21051180). 

I meant bz2105118. Thanks Jie for correcting me.
Comment 6 Coiby 2022-09-19 01:22:42 UTC 
MR: https://gitlab.com/redhat/centos-stream/rpms/kexec-tools/-/merge_requests/93
Comment 15 errata-xmlrpc 2023-05-09 08:14:41 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
Note You need to log in before you can comment on or make changes to this bug.