Bug 1897802
| Summary: | early boot: WARNING: Locking directory /run/cryptsetup is missing! | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Georg Sauthoff <fedora> |
| Component: | cryptsetup | Assignee: | Milan Broz <gmazyland> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | agk, fedoraproject, filbranden, flepied, gmazyland, lnykryn, mailinglists35, msekleta, okozina, ssahani, s, systemd-maint, voj-tech, yuwatana, zbyszek, z |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cryptsetup-2.3.5-2.fc34 cryptsetup-2.3.5-2.fc33 cryptsetup-2.3.5-2.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-03-19 20:11:46 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
Georg Sauthoff
2020-11-14 16:05:51 UTC
That message is from libcryptsetup: https://sources.debian.org/src/cryptsetup/2:2.3.4-1/lib/utils_device_locking.c/?hl=109#L109 And this message is just warning that neeeded directory is not available, so it is created as a fallback inside libcryptsetup (but with default permissons - that could be problematic). Systemd should create this directory according to provided /usr/lib/tmpfiles.d/cryptsetup.conf (part of cryptsetup-libs) before calling crypto activation. Some systemd dependency is missing here? The mix migrated to cryptsetup after all ;) https://gitlab.com/cryptsetup/cryptsetup/-/commit/1e7521c0564936fdbf098ce448e91e0ba25bffae FEDORA-2021-17c262e08d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-17c262e08d FEDORA-2021-28e528d2b6 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-28e528d2b6 FEDORA-2021-3a694e18c9 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3a694e18c9 FEDORA-2021-17c262e08d has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-17c262e08d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-17c262e08d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-3a694e18c9 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3a694e18c9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3a694e18c9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-28e528d2b6 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-28e528d2b6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-28e528d2b6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-17c262e08d has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-3a694e18c9 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-28e528d2b6 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. until this change lands in various other EL clones (centos, oracle), workaround is: # cat /etc/dracut.conf.d/99-local.conf install_items+=" /usr/lib/tmpfiles.d/cryptsetup.conf " |