Ubuntu
freeipa package

ipa-client-install fails on restarting non-existing chronyd.service

Bug #1890786 reported by Martin Pitt
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
freeipa (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Confirmed
Undecided
Unassigned

Bug Description

DistroRelease: Ubuntu 20.10
Package: freeipa-client 4.8.6-1ubuntu2

Client install fails:

 * LANG=C /usr/sbin/ipa-client-install --domain cockpit.lan --realm COCKPIT.LAN --mkhomedir --enable-dns-updates --unattended --force-join --principal admin -W --force-ntpd
Option --force-ntpd has been deprecated and will be removed in a future release.
Discovery was successful!
Client hostname: x0.cockpit.lan
Realm: COCKPIT.LAN
DNS Domain: cockpit.lan
IPA Server: f0.cockpit.lan
BaseDN: dc=cockpit,dc=lan
Synchronizing time
No SRV records of NTP servers found and no NTP server or pool address was provided.
CalledProcessError(Command ['/bin/systemctl', 'restart', 'chronyd.service'] returned non-zero exit status 5: 'Failed to restart chronyd.service: Unit chronyd.service not found.\n')
The ipa-client-install command failed. See /var/log/ipaclient-install.log for more information

/var/log/ipaclient-install.log basically says the same, just with a giant Traceback for CalledProcessError.

freeipa-client could depend on chronyd, but IMHO it would be better to make this non-fatal. If one uses systemd-timesyncd (as we do by default in Ubuntu), that should be fine?

Tags: groovy
Martin Pitt (pitti)
tags: added: groovy
Revision history for this message
paul patou (paulpatou) wrote :

Hi, I encounter the same problem on ubuntu 20.04.1, is there any news on the resolution of this bug?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in freeipa (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package freeipa - 4.8.6-1ubuntu3

---------------
freeipa (4.8.6-1ubuntu3) groovy; urgency=medium

  * fix-chrony-service-name.diff: Map to correct chrony service name.
    (LP: #1890786)
  * fix-sssd-socket-activation.diff: Don't add a 'services =' line on
    sssd.conf. (LP: #1879083)

 -- Timo Aaltonen <email address hidden> Fri, 16 Oct 2020 10:34:47 +0300

Changed in freeipa (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
David Baucum (maxolasersquad) wrote :

Any chance of getting this fixed released for Ubuntu 12.04? It is still on package 4.8.6-1ubuntu2.

Revision history for this message
Johannes Midgren (m-johannes-6) wrote :

I second @maxolasersquad's request. It's such a pity to find that a solution was implemented so long ago but still lacking in the current LTS release. This leaves FreeIPA (client install) broken in 20.04.

(The second fix is also highly anticipated since leaving the 'services' clause in the config file makes sssd (?) spin up additional unnecessary services that will always fail. These errors cause no harm though other than lost time tracking down the cause of the failed services.)

If it helps, I can confirm that applying these patches do solve both issues. Tested on updated Ubuntu 20.04.3 2021-11-05.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in freeipa (Ubuntu Focal):
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

This is *still* broken on Ubuntu 21.10 and Debian testing. However, it is subtly different, I filed bug 1966181 about it.

Revision history for this message
dmitrij (dpdpdp) wrote :

It still reproduces on 20.04

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.