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.
Created attachment 1191700[details]
grub.conf file on an EFI system with tboot installed
Description of problem:
Because grub does not support tboot launch on UEFI-based systems, tboot should not be listed among the optional packages on UEFI based systems. This should also be backported to z-stream for all RHEL-6.
If the user installs tboot on a UEFI system, s/he will not be able to boot, unless s/he knows how to edit the grub stanza in the grub pre-boot environment. This is not acceptable in any scenario, but it is catastrophic in a multi-provisioning environment.
Only one grub stanza is created, and it launches tboot (see attached).
I tried a number of things to make this unnecessary.
Exiting the tboot.spec file with nonzero status causes the provision to abort, which leaves the system in an unknown (AFICT) state.
Also tried creating an init script to uninstall tboot on shutdown, but I was unable to make that work consistently. It's the wrong approach, anyway, as the systemd mavens pointed out when I tried to do this in RHEL-7. The correct approach is not to install tboot on UEFI systems in the first place.
The only way to do that without aborting the provisioning is to not make tboot available as an option in the first place.
If a UEFI system is being provisioned,tboot must not be listed among the options.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Created attachment 1191700 [details] grub.conf file on an EFI system with tboot installed Description of problem: Because grub does not support tboot launch on UEFI-based systems, tboot should not be listed among the optional packages on UEFI based systems. This should also be backported to z-stream for all RHEL-6. If the user installs tboot on a UEFI system, s/he will not be able to boot, unless s/he knows how to edit the grub stanza in the grub pre-boot environment. This is not acceptable in any scenario, but it is catastrophic in a multi-provisioning environment. Only one grub stanza is created, and it launches tboot (see attached). I tried a number of things to make this unnecessary. Exiting the tboot.spec file with nonzero status causes the provision to abort, which leaves the system in an unknown (AFICT) state. Also tried creating an init script to uninstall tboot on shutdown, but I was unable to make that work consistently. It's the wrong approach, anyway, as the systemd mavens pointed out when I tried to do this in RHEL-7. The correct approach is not to install tboot on UEFI systems in the first place. The only way to do that without aborting the provisioning is to not make tboot available as an option in the first place. If a UEFI system is being provisioned,tboot must not be listed among the options.