Bug 2203361
Summary: | NBDE on block devices without a filesystem is broken | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Matej Marušák <mmarusak> | |
Component: | cockpit | Assignee: | Marius Vollmer <mvollmer> | |
Status: | CLOSED ERRATA | QA Contact: | Jan Ščotka <jscotka> | |
Severity: | unspecified | Docs Contact: | Mirek Jahoda <mjahoda> | |
Priority: | unspecified | |||
Version: | 9.2 | CC: | mjahoda, mpitt, release-test-team-automation | |
Target Milestone: | rc | Keywords: | Triaged, ZStream | |
Target Release: | 9.3 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | 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, 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 this update, 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: | ||||
: | 2207498 2212350 (view as bug list) | Environment: | ||
Last Closed: | 2023-11-07 08:38:39 UTC | Type: | Bug | |
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: | ||||
Bug Blocks: | 2207498, 2212350 |
Description
Matej Marušák
2023-05-12 07:29:28 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 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-2023:6591 |