Bug 982276
| Summary: | /etc/tmpfiles.d doesn't get processed inside systemd-nspawn | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nathaniel McCallum <npmccallum> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | johannbg, lnykryn, mschmidt, msekleta, notting, plautrba, systemd-maint, vpavlin, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-10 13:45:02 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
Nathaniel McCallum
2013-07-08 14:43:42 UTC
-bash-4.2# systemctl status systemd-tmpfiles-setup.service
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static)
Active: active (exited) since Mon 2013-07-08 10:13:56 EDT; 37min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 20 ExecStart=/usr/bin/systemd-tmpfiles --create --remove (code=exited, status=0/SUCCESS)
Jul 08 10:13:56 freeipa.mccallum.lan systemd[1]: Starting Recreate Volatile Files and Directories...
Jul 08 10:13:56 freeipa.mccallum.lan systemd[1]: Started Recreate Volatile Files and Directories.
-bash-4.2# cat /etc/tmpfiles.d/dirsrv-MCCALLUM-LAN.conf
d /var/run/dirsrv 0770 dirsrv dirsrv
d /var/lock/dirsrv 0770 dirsrv dirsrv
d /var/lock/dirsrv/slapd-MCCALLUM-LAN 0770 dirsrv dirsrv
-bash-4.2# ls -lh /var/lock/
total 0
drwxrwxr-x 2 root lock 40 Jul 8 10:13 lockdev
drwxr-xr-x 4 root root 80 Jul 8 10:13 pki
drwxr-xr-x 2 root root 40 Jul 8 10:13 subsys
So apparently the .conf file is being run, but the directories aren't being created. Running the exact same command manually after login properly creates the directories... (In reply to Nathaniel McCallum from comment #1) > -bash-4.2# cat /etc/tmpfiles.d/dirsrv-MCCALLUM-LAN.conf > d /var/run/dirsrv 0770 dirsrv dirsrv > d /var/lock/dirsrv 0770 dirsrv dirsrv > d /var/lock/dirsrv/slapd-MCCALLUM-LAN 0770 dirsrv dirsrv One thing that comes to mind is that on a normal Fedora system, /var/run and /var/lock are symlinks to ../run/lock and ../run, respectively. Please verify this is the case in your container. Sorry. The other way around. In /var: lock -> ../run/lock run -> ../run # ls -lhd /var/lock /var/run lrwxrwxrwx 1 root root 11 Jul 8 09:10 /var/lock -> ../run/lock drwxr-xr-x 14 root root 4.0K Jul 8 11:34 /var/run That is on a completely fresh install using the official instructions. Sounds like an iteration of: https://bugzilla.redhat.com/show_bug.cgi?id=919374 Nathaniel, is that the same issue? Did you encounter the issue when creating an OS tree with the packages where that fix to filesytem.rpm is applied? Yum creates that directory before anything else, we cannot fix that with the (fixed) filesystem.rpm alone: https://bugzilla.redhat.com/show_bug.cgi?id=975864 dnf might be fixed already: https://bugzilla.redhat.com/show_bug.cgi?id=975858 I am almost certain that this bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=975864 *** This bug has been marked as a duplicate of bug 975864 *** |