Bug 2159728
Summary: | clevis_devices_to_unlock() doesn't skip comments, causing clevis-luks-askpass.service to always run | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Martin Zelený <mzeleny> |
Component: | clevis | Assignee: | Sergio Arroutbi <sarroutb> |
Status: | CLOSED ERRATA | QA Contact: | Martin Zelený <mzeleny> |
Severity: | medium | Docs Contact: | Petr Hybl <phybl> |
Priority: | medium | ||
Version: | 9.2 | CC: | dapospis, jafiala, mjahoda, phybl, qe-baseos-security, rmetrich, sarroutb |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | Flags: | pm-rhel:
mirror+
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | clevis-18-108.el9 | Doc Type: | Bug Fix |
Doc Text: |
.Clevis now correctly skips commented-out devices in `crypttab`
Previously, Clevis tried to unlock commented-out devices in the `crypttab` file, causing the `clevis-luks-askpass` service to run even if the device was not valid. This caused unnecessary service runs and made it difficult to troubleshoot.
With this fix, Clevis ignores commented-out devices. Now, if an invalid device is commented out, Clevis does not attempt to unlock it, and `clevis-luks-askpass` finishes appropriately. This makes it easier to troubleshoot and reduces unnecessary service runs.
|
Story Points: | --- |
Clone Of: | 2159440 | Environment: | |
Last Closed: | 2023-05-09 07:46:11 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: | 2159440 | ||
Bug Blocks: |
Description
Martin Zelený
2023-01-10 14:07:35 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 (clevis 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:2321 |