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:
Nowadays it's hard to troubleshoot clevis issue happening early during boot in the initramfs phase, because even with rd.debug, clevis scripts run blindly.
This would definitely help troubleshooting when something goes wrong (PCR changes or Tang issue for example).
This can be done on RHEL/Fedora using the following snippet at the beginning of /usr/bin/clevis-luks-common-functions:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
enable_debugging() {
# Automatically enable debugging if in initramfs phase and rd.debug
if [ -e /usr/lib/dracut-lib.sh ]; then
local bashopts=$-
# Because dracut is loosely written, disable hardening options temporarily
[[ $bashopts != *u* ]] || set +u
[[ $bashopts != *e* ]] || set +e
. /usr/lib/dracut-lib.sh
[[ $bashopts != *u* ]] || set -u
[[ $bashopts != *e* ]] || set -e
fi
}
enable_debugging
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Version-Release number of selected component (if applicable):
clevis-15-1.el8.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (clevis bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:1857
Description of problem: Nowadays it's hard to troubleshoot clevis issue happening early during boot in the initramfs phase, because even with rd.debug, clevis scripts run blindly. This would definitely help troubleshooting when something goes wrong (PCR changes or Tang issue for example). This can be done on RHEL/Fedora using the following snippet at the beginning of /usr/bin/clevis-luks-common-functions: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- enable_debugging() { # Automatically enable debugging if in initramfs phase and rd.debug if [ -e /usr/lib/dracut-lib.sh ]; then local bashopts=$- # Because dracut is loosely written, disable hardening options temporarily [[ $bashopts != *u* ]] || set +u [[ $bashopts != *e* ]] || set +e . /usr/lib/dracut-lib.sh [[ $bashopts != *u* ]] || set -u [[ $bashopts != *e* ]] || set -e fi } enable_debugging -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Version-Release number of selected component (if applicable): clevis-15-1.el8.x86_64