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.

Document whether grubby --update-kernel=ALL --args should survive kernel upgrades

When testing grubby behaviour without kernelopts on RHEL 9 (see bug 2021801), I noticed that grubby --update-kernel=ALL --args is very volatile when it comes to subsequent kernel upgrades. On x86_64 it used to work on RHEL 8 but does not seem to work on RHEL 9 (bug 2021193), on s390x it only seems to work when reboot is done after grubby is run and before dnf upgrade (bug 2021207).

The expected behaviour of grubby with respect to kernel upgrades should be specifically spelled out in the product documentation, so that  we have aligned assumptions about the workflows.

Reported by: rhn-engineering-jpazdziora

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9-beta/html/managing_monitoring_and_updating_the_kernel/configuring-kernel-command-line-parameters_managing-monitoring-and-updating-the-kernel#annotations:a893c7ee-0f49-46ff-8c28-1498b186a7f3

Of course, if it gets determined that the kernel command line parameters are *not* expected to survive kernel upgrades, that is just as important to get documented as the positive case.