Bug 2107609

Summary:	[RFE] grubby doesn't list TBoot entries
Product:	Red Hat Enterprise Linux 9	Reporter:	Renaud Métrich <rmetrich>
Component:	grubby	Assignee:	Bootloader engineering team <bootloader-eng-team>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.4	CC:	jaredz, raravind, shangsong2, tcamuso
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-16 17:08:28 UTC	Type:	Story
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2107618
Bug Blocks:	2107621, 2107634, 2107635, 2111338

Description Renaud Métrich 2022-07-15 14:15:52 UTC

Description of problem:

When having TBoot configured on the system, executing `grubby --info=ALL` doesn't print TBoot entries.
This is due to `grubby` printing BLS entries only (through executing `/usr/libexec/grubby/grubby-bls` internally).
Because TBoot and BLS are incompatible for now, `grubby` needs to be enhance to print "legacy" entries found in `/boot/grub2/grub.cfg` as well.


Version-Release number of selected component (if applicable):

grubby-8.40-55.el9.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Install TBoot and regenerate the Grub menu

  # yum -y install tboot
  # grub2-mkconfig -o /etc/grub2.cfg

2. Execute `grubby --info=ALL`

Actual results:

BLS entries listed only, no TBoot entries (present in `/boot/grub2/grub.cfg`)

Expected results:

All entries displayed while booting

Comment 6 raravind 2023-07-17 17:35:43 UTC

Renaud,

This feature request cant be granted now due to following reasons:
a. Intel is looking into deprecating tboot.
b. the attached customer case is closed

Comment 7 RHEL Program Management 2023-09-16 17:07:53 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 8 RHEL Program Management 2023-09-16 17:08:28 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.