Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1476207
Description of problem: Enabling RHDS 10.1 instance service on RHEL 7 doesn't work. Administration manual states that to enable instance service is done by running systemctl enable dirsrv@instance_name However, this doesn't survive restart. Searching for enabled units gives: [root@host-172-16-64-130 ~]# systemctl list-unit-files | grep enabled | grep dirsrv dirsrv@.service enabled Version-Release number of selected component (if applicable): RHDS 10 How reproducible: always Steps to Reproduce: 1. create RHDS instance 'abc' 2. run systemctl enable dirsrv@abc 3. restart machine Actual results: dirsrv@abc is not running Expected results: dirsrv@abc is running Additional info: enabling all instances (systemctl enable dirsrv.target) works. Not surre if it's a bug in documentation or sysmted unit files (seems to me more likely). OS: Red Hat Enterprise Linux Server release 7.3 (Maipo) RHDS: redhat-ds-10.1.0-2.el7dsrv.x86_64
Metadata Update from @firstyear: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1476207
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.7.0 (was: 0.0 NEEDS_TRIAGE)
The issue here is that we have our own target. I think we can fix this by changing our .service to use multi-user.target instead, but vwe have to keep dirsrv.target for legacry :(
Metadata Update from @firstyear: - Issue assigned to firstyear
<img alt="0001-Ticket-49378-server-init-fails.patch" src="/389-ds-base/issue/raw/files/9f43e2d45818aa9adba4bea8a41f732c565a5e03510c24b984a808e2759cabbc-0001-Ticket-49378-server-init-fails.patch" />
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to review (was: None)
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: review)
commit e9ad5f5 To ssh://git@pagure.io/389-ds-base.git af723fd..e9ad5f5 master -> master
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
7b960ba..4875300 389-ds-base-1.3.7 -> 389-ds-base-1.3.7
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/2437
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.