Description of problem: When booting from a luks-encrypted root fs systemd-cryptsetup issues the following warning: systemd-cryptsetup[385]: WARNING: Locking directory /run/cryptsetup is missing! Version-Release number of selected component (if applicable): systemd-udev-246.6-3.fc33.x86_64 How reproducible: always Steps to Reproduce: 1. install Fedora with luks-encryption enabled 2. boot 3. search journalctl -b for this warning Actual results: systemd-cryptsetup.* WARNING: Locking directory /run/cryptsetup is missing! Expected results: No such warning. Additional info:
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?
https://github.com/systemd/systemd/pull/18448
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 "