Bug 1108224

Summary:	Replace ntpdate calls with ntpd
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Kosek <mkosek>
Component:	ipa	Assignee:	Martin Kosek <mkosek>
Status:	CLOSED ERRATA	QA Contact:	Namita Soman <nsoman>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.1	CC:	rcritten, xdong
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ipa-4.0.3-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 10:11:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Kosek 2014-06-11 14:57:48 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3797

Ntpdate is being slowly deprecated(as of Fedora 20). We should replace time sync using ntpdate with ntpd.

Currently we use ntpdate to sync the time for the KDC prior to client enrollment in ipa-client-install.

Running ntpd with -g option should handle it.

Comment 1 Martin Kosek 2014-06-11 15:23:26 UTC

This request is already fixed in upstream FreeIPA project. Please refer to the linked ticket for additional details and related commits.

Comment 3 Xiyang Dong 2015-01-28 18:57:21 UTC

Verified on ipa-client-4.1.0-15.el7.x86_64:

[root@beast ~]# systemctl disable chronyd
rm '/etc/systemd/system/multi-user.target.wants/chronyd.service'

[root@beast ~]# ipa-client-install -p $ADMINID -w $ADMINPW -U  --debug
.
.
.
Synchronizing time with KDC...
Search DNS for SRV record of _ntp._udp.testrelm.test
DNS record found: 0 100 123 mgmt9.testrelm.test.
DNS record found: 0 100 123 cloud-qe-19.testrelm.test.
Starting external process
args='/usr/sbin/ntpd' '-qgc' '/tmp/tmpEoLvCy'
Process finished, return code=0
stdout=ntpd: time slew -0.006790s
.
.
.

Comment 5 errata-xmlrpc 2015-03-05 10:11:51 UTC

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-0442.html