Red Hat Bugzilla – Bug 824495
ipactl.service fails on boot - but not if manually started
Last modified: 2013-11-29 06:11:18 EST
+++ This bug was initially created as a clone of Bug #806424 +++
Description of problem:
The ipactl.service fails on boot, but not if it is subsequently restarted manually on boot up
Version-Release number of selected component (if applicable):
Installed freeipa as per the instructions on the Fedora web site and ipactl.service always fails on boot up but not if restarted manually
Steps to Reproduce:
It should start up
It does not start
I've worked around this by doing a systemctl enable dirsrv.target and now the ipactl.service does start on boot. What "seems" to happen is that ipactl starts the 389 directory server but as far as systemd is concerned that target (dirsrv.target) isn't wanted so it immediately shuts it down. Then the subsequent services that ipactl tries to start fail because they can't contact the 389 directory service. By explicitly enabling the dirsrv.target - it does not get shutdown by systemd.
With systemd supposedly being all singing - all dancing - is ipactl the correct thing to do - or should it be properly converted so that systemd itself starts the required services? At the very least it would appear the ipactl.service may need a dependency on dirsrv.target adding.
This is known to work in current RHEL-7.0 version, upstream version was also closed some time ago. Closing the bug.