This bug was fixed in the package freeipa - 3.3.4-0ubuntu4

freeipa (3.3.4-0ubuntu4) utopic; urgency=medium

  * fix-ntp-paths.diff: Don't use fedora paths for ntpd options. (LP:
  * add-debian-platform.diff: Let testing chronyd always return false,
    since the package already conflicts with ntp so can't be
    installed/enabled at the same time. Allows configuring ntpd without
    forcing it. (LP: #1309655)
 -- Timo Aaltonen <>   Tue, 05 Aug 2014 18:59:50 +0300

** Changed in: freeipa (Ubuntu)
       Status: Triaged => Fix Released

You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.

  freeipa-client-install points to wrong ntp.conf file

Status in “freeipa” package in Ubuntu:
  Fix Released
Status in “freeipa” source package in Trusty:
  In Progress

Bug description:
  On a fresh 14.04-server install freeipa-client-install does not write
  to the correct ntpd conf file. Using

  ipa-client-install --enable-dns-updates --force-ntpd

  it tries writing to:


  Which is not a correct path on Ubuntu

  It needs to be /etc/default/ntpdate and /etc/default/ntp

  Other than that, the client actually work! It joins the domain, pushes
  a DNS entry, and users are able to login :)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to