Back to bug 2207498

Who When What Removed Added
Red Hat Bugzilla 2023-05-16 07:09:44 UTC Pool ID sst_cockpit_rhel_9
Red Hat One Jira (issues.redhat.com) 2023-05-16 07:10:35 UTC Link ID Red Hat Issue Tracker RHELPLAN-157304
Martin Pitt 2023-05-16 07:11:57 UTC Status NEW MODIFIED
Target Release --- 9.2
Martin Pitt 2023-05-16 08:08:03 UTC Link ID Github cockpit-project/cockpit/pull/18698
errata-xmlrpc 2023-05-16 18:53:22 UTC Fixed In Version cockpit-286.2-1.el9_2
Status MODIFIED ON_QA
Mirek Jahoda 2023-05-31 10:28:05 UTC Docs Contact mjahoda
Martin Pitt 2023-06-05 11:35:40 UTC Depends On 2212350
Jan Ščotka 2023-07-18 07:43:29 UTC Status ON_QA VERIFIED
Mirek Jahoda 2023-07-31 14:07:51 UTC Doc Text .The web console NBDE binding steps now work also on volume groups with a root file system

In RHEL 9.2.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/114264
[RHBA-2023:114264] 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.
Doc Type If docs needed, set a value Bug Fix
errata-xmlrpc 2023-08-01 00:01:43 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-08-01 08:49:34 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2023-08-01 08:49:34 UTC
errata-xmlrpc 2023-08-01 08:49:35 UTC Link ID Red Hat Product Errata RHBA-2023:4346
Mirek Jahoda 2023-08-01 09:44:35 UTC Doc Text .The web console NBDE binding steps now work also on volume groups with a root file system

In RHEL 9.2.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/114264
[RHBA-2023:114264] 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 9.2.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:4346
[RHBA-2023:4346] 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-08-01 15:37:50 UTC Doc Text .The web console NBDE binding steps now work also on volume groups with a root file system

In RHEL 9.2.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:4346
[RHBA-2023:4346] 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 9.2.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:4346[RHBA-2023:4346] 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 2207498