[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2022-03-24 Thread dmitrij
It still reproduces on 20.04

-- 
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


___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp


[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2022-03-24 Thread Martin Pitt
This is *still* broken on Ubuntu 21.10 and Debian testing. However, it
is subtly different, I filed bug 1966181 about it.

-- 
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


___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp


[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2022-03-24 Thread Martin Pitt
** 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


___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp


[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2021-11-06 Thread Johannes Midgren
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.

-- 
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

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


___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp


[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2021-01-25 Thread David Baucum
Any chance of getting this fixed released for Ubuntu 12.04? It is still
on package 4.8.6-1ubuntu2.

-- 
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

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

___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp


[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2020-10-17 Thread Launchpad Bug Tracker
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   Fri, 16 Oct 2020 10:34:47 +0300

** Changed in: freeipa (Ubuntu)
   Status: Confirmed => 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/1890786

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

Status in freeipa package in Ubuntu:
  Fix Released

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

___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp


[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2020-09-30 Thread paul patou
Hi, I encounter the same problem on ubuntu 20.04.1, is there any news on
the resolution of this bug?

-- 
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:
  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

___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp


[Freeipa] [Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2020-09-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: freeipa (Ubuntu)
   Status: New => Confirmed

-- 
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:
  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

___
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help   : https://help.launchpad.net/ListHelp