Bug 1676898
Summary: | luksmeta does not work properly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dahlhoff <benjamin.dahlhoff> |
Component: | luksmeta | Assignee: | Daniel Kopeček <dkopecek> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | agk, arstedt, benjamin.dahlhoff, dkopecek, npmccallum |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-03-26 13:07:27 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: |
Description
Dahlhoff
2019-02-13 14:31:59 UTC
luksmeta *never* changes whether or not there is an active LUKS slot. Doing so is a layering violation. The commands are working as designed. Please use cryptsetup to remove LUKS slots. From the documetation: "Although the luksmeta slots are inspired by the LUKS slots, they are functionally independent and share only a casual relationship. Slots merely provide a hint that a given chunk of metadata is associated with a specific LUKSv1 password (in a slot with the same number)." |