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.
Bug 2207498 - NBDE on block devices without a filesystem is broken [rhel-9.2.0.z]
Summary: NBDE on block devices without a filesystem is broken [rhel-9.2.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: cockpit
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.2
Assignee: Marius Vollmer
QA Contact: Jan Ščotka
Mirek Jahoda
URL:
Whiteboard:
Depends On: 2203361 2212350
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-16 07:09 UTC by RHEL Program Management Team
Modified: 2023-09-20 16:26 UTC (History)
3 users (show)

Fixed In Version: cockpit-286.2-1.el9_2
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 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.
Clone Of: 2203361
Environment:
Last Closed: 2023-08-01 08:49:34 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github cockpit-project cockpit pull 18698 0 None Merged storage: When fixing NBDE, also recognize indirect root filesystems 2023-05-16 08:08:02 UTC
Red Hat Issue Tracker RHELPLAN-157304 0 None None None 2023-05-16 07:10:35 UTC
Red Hat Product Errata RHBA-2023:4346 0 None None None 2023-08-01 08:49:35 UTC

Comment 10 errata-xmlrpc 2023-08-01 08:49:34 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 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:4346


Note You need to log in before you can comment on or make changes to this bug.