Testing with 1.2.11.16 on f17 with no existing instances:

/bin/systemctl is-active dirsrv.target
unknown

/bin/systemctl start dirsrv.target
Failed to issue method call: Unit dirsrv.target failed to load: No such file or directory. See system logs and 'systemctl status dirsrv.target' for details.

echo $?
1

Looks like this might be fixed in the most recent version. Are there any other details or steps I need to reproduce this?

rcrit,

Have you seen this update? Is this still an issue? Or am I missing a step?

Mark

If there is no update this will be closed at the end of the week.

Mark

I can't reproduce the is-active bug in F-18.

The start when no instances are not configured still returns 0 but looking at the systemctl man page this seems a bit undefined, so it may not be a problem. Only the active thing was causing freeipa grief.

I think this can be closed.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/459

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.