Bug 2126959
| Summary: | must handle clevis-luks-askpass and clevis-luks-askpass@ systemd unit names | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Rich Megginson <rmeggins> | |
| Component: | rhel-system-roles | Assignee: | Sergio Correia <scorreia> | |
| Status: | CLOSED ERRATA | QA Contact: | Evgeny Fedin <efedin> | |
| Severity: | unspecified | Docs Contact: | Mirek Jahoda <mjahoda> | |
| Priority: | unspecified | |||
| Version: | 9.2 | CC: | djez, efedin, mturner, scorreia, spetrosi | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | 9.2 | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | role:nbde_client | |||
| Fixed In Version: | rhel-system-roles-1.21.0-0.7.el9 | Doc Type: | Bug Fix | |
| Doc Text: |
.The `nbde_client` System Role now correctly handles different names of `clevis-luks-askpass`
The `nbde_client` System Role has been updated to handle the systems on which the `clevis-luks-askpass` `systemd` unit has a different name. The role now correctly works with different names of `clevis-luks-askpass` on managed nodes, which requires unlocking also LUKS-encrypted volumes that mount late in the boot process.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2126960 (view as bug list) | Environment: | ||
| Last Closed: | 2023-05-09 07:37:53 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: | ||||
| Bug Blocks: | 2126960 | |||
|
Description
Rich Megginson
2022-09-14 23:13:32 UTC
See https://github.com/linux-system-roles/nbde_client/pull/79 for additional information and an alternate approach - but I think it is better for the role to handle this rather than the user having to know which form to use. 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 (rhel-system-roles 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/RHEA-2023:2246 |