freeipa team mailing list archive

[Launchpad Bug Tracker <1309655@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package freeipa - 3.3.4-0ubuntu3.1

---------------
freeipa (3.3.4-0ubuntu3.1) trusty-proposed; urgency=medium

  * fix-ntp-paths.diff: Don't use fedora paths for ntpd options. (LP:
    #1309655)
  * 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 <tjaalton@xxxxxxxxxx>   Tue, 05 Aug 2014 18:59:50 +0300

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

-- 
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1309655

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

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

Bug description:
  [Impact]
  On a fresh 14.04-server install freeipa-client-install does not write to the correct ntpd conf file. Also, it needs --force-ntpd option to overcome a fault where the installer falsely detects chronyd being installed.

  [Test case]
  Using

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

  it tries writing to:

  /etc/sysconfig/ntpd

  Which is not a correct path on Ubuntu

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

  [Regression potential]
  None, the patch fixes a path. For chronyd it just skips is_enabled() for it, and since freeipa-client depends on ntp and chrony conflicts with ntp, there's no way chrony is installed with freeipa-client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1309655/+subscriptions