Bug 2212371

Summary:	NBDE on block devices without a filesystem is broken [rhel-8.8.0.z]
Product:	Red Hat Enterprise Linux 8	Reporter:	RHEL Program Management Team <pgm-rhel-tools>
Component:	cockpit-appstream	Assignee:	Martin Pitt <mpitt>
Status:	CLOSED ERRATA	QA Contact:	Jan Ščotka <jscotka>
Severity:	unspecified	Docs Contact:	Mirek Jahoda <mjahoda>
Priority:	unspecified
Version:	8.8	CC:	jscotka, mjahoda, mmarusak, mpitt, mvollmer, release-test-team-automation
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	8.8	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-appstream-286.2-1.el8_8	Doc Type:	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://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.	Story Points:	---
Clone Of:	2212350	Environment:
Last Closed:	2023-06-27 14:58:09 UTC	Type:	---
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:	2212350
Bug Blocks:

Comment 7 errata-xmlrpc 2023-06-27 14:58:09 UTC

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 (cockpit-appstream bug fix 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-2023:3829