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:
If tboot is installed and active, and the kernel package is updated with "yum update kernel", the tboot entry in /boot/grub2/grub.cfg or /boot/efi/EFI/redhat/grub.cfg still refer to the old kernel package

Version-Release number of selected component (if applicable):
grubby-8.28-17.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. configure RHEL 7.2 for booting with tboot
2. update the kernel package

Actual results:
The "boot" boot entry is still the same as before, referencing the previous kernel. This will be so even if that kernel has been uninstalled.

Expected results:
tboot entries are added for the new kernel, or changed from the old one to the new one.

Additional info:
This is because the kernel %post script just calls grubby to an entry, and grubby doesn't support tboot.

WORKAROUND: manually run grub2-mkconfig as appropriate for the system (legacy or UEFI) after the kernel update.

Please attach the config file as it appears and how it's supposed to appear.

Changing needinfo, as Martin is no longer at Fujitsu Technology Solutions.
Japanese divisions have taken over the bugzillas.

Sugimoto-san,

Can you reply to Comment2 ?

Regards,
Nagahama

Please see https://bugzilla.redhat.com/show_bug.cgi?id=1486454#c3

Dear RedHat,

I'm sorry for my very late response.

Bill-san, Thank you for your information.

We cannot reproduce this problem now. 

Please close this ticket once. 

Best Regard,
Koji Sugimoto