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.

osbuild when building images for S390x, such as the 8.4 guest images, follows the kernel-install(8) specification and sets the kernel command line via "/etc/kernel/cmdline". This is also already respected respected on platforms that use grub, via `20-grub.install`. But when using grub2-mkconfig, the file is not read, leading to a loss of kernel command line options.

If grub2-mkconfig was to first read, `/etc/kernel/cmdline`, before sourcing `/etc/default/grub`, the new way and the old way could be supported at the same time.

and the grubby tool also needs to learn about /etc/kernel/cmdline

What about having grub2-mkconfig *also* write to /etc/kernel/cmdline when building the kernel opts?
I'd expect this to then be used by /usr/lib/kernel/install.d/20-grub.install instead of using /proc/cmdline which may contain non-persistent options.

Example with this scenario:

1. Boot with "rd.debug"

2. Update the kernel

  This will create a BLS entry containing "rd.debug" which is non-sense, due to not relying on content of /etc/kernel/cmdline but /proc/cmdline

(In reply to Renaud Métrich from comment #7)
> What about having grub2-mkconfig *also* write to /etc/kernel/cmdline when
> building the kernel opts?

Yes, agreed. It should do both.

Same for grubby as mentioned in Comment 6.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.