Bug 1643686
Summary: | Wrong slot number message | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tamás Szekeres <szekeres.tamas> |
Component: | cryptsetup | Assignee: | Milan Broz <gmazyland> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | agk, gmazyland, okozina |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cryptsetup-2.0.5-1.fc28 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-11-17 05:22:17 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
Tamás Szekeres
2018-10-27 10:48:31 UTC
Yes, it is a bug, it actually prints "removed keyslot 0" everytime in luksKillKeyslot, because it misinterprets exit code from crypt_keyslot_destroy(). But it is just error in message, code wipes the proper keyslot. Will be fixed in 2.0.5 (that will be released very soon), thanks! This is the upstream commit fixing the issue https://gitlab.com/cryptsetup/cryptsetup/commit/7213d5a76bfcea01a531d2d39e0766fa4d92cb94 Thanks for your time! cryptsetup-2.0.5-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8936092f99 cryptsetup-2.0.5-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8936092f99 cryptsetup-2.0.5-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. |