Back to bug 2212371

Who When What Removed Added
Red Hat Bugzilla 2023-06-05 12:58:15 UTC Pool ID sst_cockpit_rhel_8
Red Hat One Jira (issues.redhat.com) 2023-06-05 12:59:36 UTC Link ID Red Hat Issue Tracker RHELPLAN-158968
Martin Pitt 2023-06-05 13:02:50 UTC Summary NBDE on block devices without a filesystem is broken [rhel-8.9] [rhel-8.8.0.z] NBDE on block devices without a filesystem is broken [rhel-8.8.0.z]
Status NEW POST
Target Release --- 8.8
Mirek Jahoda 2023-06-05 13:06:40 UTC Docs Contact mjahoda
Martin Pitt 2023-06-05 14:42:15 UTC Fixed In Version cockpit-appstream-286.2-1.el8_8
Status POST MODIFIED
errata-xmlrpc 2023-06-05 18:47:01 UTC Status MODIFIED ON_QA
YunmingYang 2023-06-06 06:55:29 UTC QA Contact yunyang jscotka
Jan Ščotka 2023-06-21 13:03:07 UTC Status ON_QA VERIFIED
errata-xmlrpc 2023-06-27 00:02:30 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-06-27 14:58:09 UTC Resolution --- ERRATA
Status RELEASE_PENDING CLOSED
Last Closed 2023-06-27 14:58:09 UTC
errata-xmlrpc 2023-06-27 14:58:11 UTC Link ID Red Hat Product Errata RHBA-2023:3829
Mirek Jahoda 2023-07-31 11:43:57 UTC Doc Type If docs needed, set a value Bug Fix
Doc Text .The web console NBDE binding steps now work also on volume groups with a root file system

In RHEL 8.8.0, due to a bug in the code for determining whether or not the user was adding a Tang key to the root file system, the binding process in the web console crashed when there was no file system on the LUKS container at all. Because the web console displayed the error message `TypeError: Qe(...) is undefined` after you had clicked the `Trust key` button in the `Verify key` dialog, you had to perform all the required steps in the command-line interface in the described scenario.

With the release of the link:https://errata.devel.redhat.com/advisory/112726[RHBA-2023:112726] advisory, the web console correctly handles additions of Tang keys to root file systems. As a result, the web console finishes all binding steps required for the automated unlocking of LUKS-encrypted volumes using Network-Bound Disk Encryption (NBDE) in various scenarios.
Mirek Jahoda 2023-07-31 14:51:33 UTC Doc Text .The web console NBDE binding steps now work also on volume groups with a root file system

In RHEL 8.8.0, due to a bug in the code for determining whether or not the user was adding a Tang key to the root file system, the binding process in the web console crashed when there was no file system on the LUKS container at all. Because the web console displayed the error message `TypeError: Qe(...) is undefined` after you had clicked the `Trust key` button in the `Verify key` dialog, you had to perform all the required steps in the command-line interface in the described scenario.

With the release of the link:https://errata.devel.redhat.com/advisory/112726[RHBA-2023:112726] advisory, the web console correctly handles additions of Tang keys to root file systems. As a result, the web console finishes all binding steps required for the automated unlocking of LUKS-encrypted volumes using Network-Bound Disk Encryption (NBDE) in various scenarios.
.The web console NBDE binding steps now work also on volume groups with a root file system

In RHEL 8.8.0, due to a bug in the code for determining whether or not the user was adding a Tang key to the root file system, the binding process in the web console crashed when there was no file system on the LUKS container at all. Because the web console displayed the error message `TypeError: Qe(...) is undefined` after you had clicked the `Trust key` button in the `Verify key` dialog, you had to perform all the required steps in the command-line interface in the described scenario.

With the release of the link:https://access.redhat.com/errata/RHBA-2023:3829[RHBA-2023:3829] advisory, the web console correctly handles additions of Tang keys to root file systems. As a result, the web console finishes all binding steps required for the automated unlocking of LUKS-encrypted volumes using Network-Bound Disk Encryption (NBDE) in various scenarios.

Back to bug 2212371