freeipa team mailing list archive
-
freeipa team
-
Mailing list archive
-
Message #01127
[Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service
** Also affects: freeipa (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1890786
Title:
ipa-client-install fails on restarting non-existing chronyd.service
Status in freeipa package in Ubuntu:
Fix Released
Status in freeipa source package in Focal:
Confirmed
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1890786/+subscriptions
References