Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1171355 - start dirsrv after chrony
start dirsrv after chrony
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
7.0
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Noriko Hosoi
Viktor Ashirov
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-05 18:56 EST by Noriko Hosoi
Modified: 2015-03-05 04:39 EST (History)
3 users (show)

See Also:
Fixed In Version: 389-ds-base-1.3.3.1-10.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 04:39:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
bootchart (365.23 KB, image/svg+xml)
2014-12-25 19:06 EST, Viktor Ashirov
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0416 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 09:26:33 EST

  None (edit)
Description Noriko Hosoi 2014-12-05 18:56:50 EST
> Starting from RHEL7 ntpd is not the default time sync daemon any more. The new time sync daemon is chronyd.service for systemctl

See https://fedorahosted.org/389/ticket/47574#comment:16
Comment 2 Viktor Ashirov 2014-12-25 19:06:25 EST
Created attachment 973094 [details]
bootchart

I made a bootchart. It shows that ns-slapd starts after chronyd. 

The only thing is that dirsrv.target still mentions ntpd.service. But since "After=" section in dirsrv@.service contains "chronyd.service", it works as expected.

Marking as VERIFIED
Comment 3 Viktor Ashirov 2014-12-25 19:07:30 EST
$ rpm -qa | grep 389
389-ds-base-debuginfo-1.3.3.1-10.el7.x86_64
389-ds-base-1.3.3.1-10.el7.x86_64
389-ds-base-libs-1.3.3.1-10.el7.x86_64
Comment 5 errata-xmlrpc 2015-03-05 04:39:59 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0416.html

Note You need to log in before you can comment on or make changes to this bug.