freeipa team mailing list archive

[ Christian Ehrhardt  <1778911@xxxxxxxxxxxxxxxxxx>]

Currently we have these:
Reverse-Recommends
==================
* ceph-base                     (for chrony)

This is the same case as with Freeipa.

* radioclk                      (for chrony)

This is meant to provide DCF77 input to chrony, so ok

Reverse-Depends
===============
* freeipa-client                (for chrony)
* freeipa-server                (for chrony)

This is how this bug was reported.
I think it is a common and working resolution to depend on the current timeserver.
I'd vote for the Depends becoming recommends so that admins can remove the package if wanted.

* gce-compute-image-packages    (for chrony)

That is an intentional "there you should sync with that" AFAIK. keeping
as-is IMHO

* maas-rack-controller          (for chrony)
* maas-region-api               (for chrony)

I know for MAAS that they really want this, even on a Container, so considering them ok'ish.
They even modify chrony.conf and such, so there a depends is correct.


In general I think the Ceph approach is good, keeping it as a recommends allows to remove it if needed. BTW Chrony on Containers will by default only serve the local time as syncing it would not work (CAP_SYS_TIME) anyway - so not much lost.

systemd-timesyncd is "only" SNTP which has to be considered inferior to
full ntp syncing.

For Ceph and Freeipa once being a recommends, I'd wish there would be a
dependency that says "but not in containers", but there is none.

** Also affects: ceph (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: ceph (Ubuntu)
       Status: New => Invalid

** Also affects: maas (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: maas (Ubuntu)
       Status: New => Invalid

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

Title:
  freeipa-client hard depends on chrony

Status in ceph package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in freeipa package in Ubuntu:
  Triaged
Status in maas package in Ubuntu:
  Invalid

Bug description:
  That freeipa-client needs accurate time to work is obvious. But there are various ways to go about this:
  1) install a  timeserver like chrony or ntp
  2) Not at all, because the system is an lxc client and thus the time is synced externally.

  Currently chrony is installed, and another package requires ntp.
  Furthermore puppet is running on the host and installs chrony on one
  run and in the next run ntp etc etc. And that on a host which requires
  neither.

  There are many ways to solve this problem with various levels of being
  accurate. Please think the problem through in such a way that all
  possible scenarios are covered.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chrony 3.2-4ubuntu4.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jun 27 14:40:03 2018
  SourcePackage: chrony
  UpgradeStatus: No upgrade log present (probably fresh install)

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