Description of problem: The fedora-domainname.service with default dependencies creates a cycle on system boot up, which makes systemd remove the fedora-domainname job. As a result, NIS domain name is not set (which is the sole purpose of this service). Setting DefaultDependencies=no solves the issue. Version-Release number of selected component (if applicable): systemd-208-14.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. # systemctl enable fedora-domainname.service 2. # reboot Actual results: fedora-domainname is not started on startup Expected results: fedora-domainname is started
fixed in upstream git.
The problem is also present (and is cured in the same way) in systemd-208-15.fc20.i686
Hello Lukas, this Bugzilla is now in limbo for 3 weeks, with a patch upstream. As it is blocking FreeIPA SUDO integration feature patches, would you please consider releasing it to Fedora 20+ to unblock our development?
initscripts-9.51-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/initscripts-9.51-2.fc20
Package initscripts-9.51-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.51-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-4376/initscripts-9.51-2.fc20 then log in and leave karma (feedback).
initscripts-9.51-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.