Description of problem: systemd-tmpfiles executes home.conf resulting in an attempt to automount /home before network is started. This does not work, and systemd fails to boot Version-Release number of selected component (if applicable): # rpm -q systemd systemd-229-7.fc24.x86_64 # rpm -q --whatprovides /usr/lib/tmpfiles.d/home.conf systemd-229-7.fc24.x86_64 How reproducible: Always Additional info: /etc/fstab: xxx:/home /home nfs defaults,comment=systemd.automount 0 0
Moving /usr/lib/tmpfiles.d/home.conf away, results in normal boot ;-)
Maybe tmpfiles should ignore paths which are configured mountpoints. This could be implemented as asking systemd for the unit for the mount path, and if this gives back a mount or automount unit, ignore the config in tmpfiles. (In reply to Kim Bisgaard from comment #1) > Moving /usr/lib/tmpfiles.d/home.conf away, results in normal boot ;-) You can instead "touch /etc/tmpfiles.d/home.conf". This has the advantage that it'll survive the next update of systemd.rpm.
Confirmed that this is still the case in Fedora 25. A fix from Debain https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805553 pointed me in the right direction: if the entry in home.conf for /home has "v" in stead of "Q", all works fine. Or better, copy home./conf from /usr/lib/tmpfiles.d to /etc/tmpfiles.d so it is safe from updates as well: sed 's/^Q/v/' < /usr/lib/tmpfiles.d/home.conf > /etc/tmpfiles.d/home.conf BTW: Fedora 23 had a "v" in this place. Q seems to have something to do with quota groups and as fas as I can understand from the tmpfiles.d man page, this is for btrfs, which I don't use, so for me, changing the Q to v in the
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Situation is exactly the same in Fedora 25 and 26 beta (haven't tried Fedora 26 final yet), so please reopen and apply fix
re-opened and changed to f25 as David requested
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 seems fine without modifying the setup. Thanks for fixing (whatever the fix was).
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.