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.
Description of problem:
Sorry for the title, I don't know how to briefly explain this...
Say the user is currently running "kernel-rt-core" while still having "kernel-core" installed in parallel.
When he updates the kernel through just using "yum update", say "kernel-core" gets an update, the latter will become the default, ending with not running the RT kernel anymore.
Reproducing this on my RHEL8 system, I can see grub2-get-kernel-settings relies on /etc/sysconfig/kernel to determine if latest should be used:
~~~
$ grep -v ^# /etc/sysconfig/kernel
UPDATEDEFAULT=yes
DEFAULTKERNEL=kernel-core
~~~
From the variable names above, I would expect the "family" of the default kernel to be selected based on DEFAULTKERNEL setting.
But nowhere this is taken into account, explaining the issue.
Version-Release number of selected component (if applicable):
grub2-tools-minimal-2.02-123.el8_6.8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install "kernel-rt-core" on a system running "kernel-core"
Actual results:
"kernel-rt-core" release becomes the default for next boots
Expected results:
only the latest "kernel-core" installation should be used as default
Additional info:
DEFAULTKERNEL seems deprecated and ignored with the new /usr/lib/kernel/install.d mechanism.
Still this needs to be taken into account.
If relying on this is not welcome anymore, then another mechanism has to be used to distinguish between kernel families, for example the following piece of code:
~~~
KERNEL_CURRENT=$(uname -r)
if [[ $KERNEL_VERSION == *.rt* && $KERNEL_CURRENT != *.rt* ]] || \
[[ $KERNEL_VERSION != *.rt* && $KERNEL_CURRENT == *.rt* ]]; then
...
fi
~~~
which enables to find out if the kernel being installed ($KERNEL_VERSION) is of same family as currently running one.
The weakness of this is this doesn't work for other kernel namings (here above I check on "rt" naming).
Comment 8RHEL Program Management
2023-09-16 17:08:04 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9RHEL Program Management
2023-09-16 17:13:17 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Sorry for the title, I don't know how to briefly explain this... Say the user is currently running "kernel-rt-core" while still having "kernel-core" installed in parallel. When he updates the kernel through just using "yum update", say "kernel-core" gets an update, the latter will become the default, ending with not running the RT kernel anymore. Reproducing this on my RHEL8 system, I can see grub2-get-kernel-settings relies on /etc/sysconfig/kernel to determine if latest should be used: ~~~ $ grep -v ^# /etc/sysconfig/kernel UPDATEDEFAULT=yes DEFAULTKERNEL=kernel-core ~~~ From the variable names above, I would expect the "family" of the default kernel to be selected based on DEFAULTKERNEL setting. But nowhere this is taken into account, explaining the issue. Version-Release number of selected component (if applicable): grub2-tools-minimal-2.02-123.el8_6.8.x86_64 How reproducible: Always Steps to Reproduce: 1. Install "kernel-rt-core" on a system running "kernel-core" Actual results: "kernel-rt-core" release becomes the default for next boots Expected results: only the latest "kernel-core" installation should be used as default Additional info: DEFAULTKERNEL seems deprecated and ignored with the new /usr/lib/kernel/install.d mechanism. Still this needs to be taken into account. If relying on this is not welcome anymore, then another mechanism has to be used to distinguish between kernel families, for example the following piece of code: ~~~ KERNEL_CURRENT=$(uname -r) if [[ $KERNEL_VERSION == *.rt* && $KERNEL_CURRENT != *.rt* ]] || \ [[ $KERNEL_VERSION != *.rt* && $KERNEL_CURRENT == *.rt* ]]; then ... fi ~~~ which enables to find out if the kernel being installed ($KERNEL_VERSION) is of same family as currently running one. The weakness of this is this doesn't work for other kernel namings (here above I check on "rt" naming).