This will fix that the upgrade "fails" as chrony will become more tolerant to the systemd change. do-release-upgrade will still remove chrony on upgrade.
I filed an extra bug for that to keep the discussions separate. => see bug 1872902 ** Description changed: [Impact] - * When chrony is removed the systems default time service is tried to be - restored. That was and is systemd-timesyncd. - - this was in Debian and Ubuntu since [1] + * When chrony is removed the systems default time service is tried to be + restored. That was and is systemd-timesyncd. + - this was in Debian and Ubuntu since [1] - * That worked fine when systemd-timesyncd was always installed as it was - in the past. But systemd 245.4-2ubuntu1 chnged that and it will no more - be installed as it now conflicts. + * That worked fine when systemd-timesyncd was always installed as it was + in the past. But systemd 245.4-2ubuntu1 changed that and it will no more + be installed as it now conflicts. - * That change in systemd lets chrony upgrade fail in postrm where it tries - to start the default again. The Bionic version of the postrm never had - the safety ||true as that was never needed in Bionic an SRU would just - have been forcing many users into a download they would not have needed. + * That change in systemd lets chrony upgrade fail in postrm where it tries + to start the default again. The Bionic version of the postrm never had + the safety ||true as that was never needed in Bionic an SRU would just + have been forcing many users into a download they would not have needed. - * But due to the systemd change in focal we now need that simple change to - avoid upgrades breaking. + * But due to the systemd change in focal we now need that simple change to + avoid upgrades breaking. - - [1]: https://salsa.debian.org/debian/chrony/-/commit/f4ecee0288b73331a4cfe6687b936fec78be4e15 - + [1]: + https://salsa.debian.org/debian/chrony/-/commit/f4ecee0288b73331a4cfe6687b936fec78be4e15 [Test Case] - * Take a bionic system with chrony installed. - Upgrade to Focal (which at least needs to have systemd 245.4-2ubuntu1 to - trigger the issue. - TODO: add some more details once exercised once + * Take a bionic system with chrony installed and upgrade to Focal + Details: + - get bionic system + - apt update && apt dist-upgrade + - apt install chrony + - do-release-upgrade -d + + Without the fix in Bionic this will crash when chrony is removed. + With the fix that will show a warning if systemd-timesyncd is + unavailable, but it won't crash the upgrade. + [Regression Potential] - * The change is minimal as it only ignores a potential error that - a) is considered safe if it happens - b) we now know will happen on a bionic->focal upgrade - In addition we also had that change since 19.10. + * The change is minimal as it only ignores a potential error that + a) is considered safe if it happens + b) we now know will happen on a bionic->focal upgrade + In addition we also had that change since 19.10. [Other Info] - - * This is of some extra urgency as it needs to land in Bionic before - upgrading to 20.04 will happen which people are supposed to test - now and will be released soon. - * Note: In focal we can now stop starting the systemd-timesyncd from - chrony as it now takes care in systemd-timesyncd.postinst. This change - will get to Focal to silence the warning, but it isn't gating the SRU to - bionic (the change we backport is already in >=19.10). + + * This is of some extra urgency as it needs to land in Bionic before + upgrading to 20.04 will happen which people are supposed to test + now and will be released soon. + * Note: In focal we can now stop starting the systemd-timesyncd from + chrony as it now takes care in systemd-timesyncd.postinst. This change + will get to Focal to silence the warning, but it isn't gating the SRU to + bionic (the change we backport is already in >=19.10). + In bionic we can't drop it the same way as we will do in Focal as there + timesyncd is not split, so the restart there was and still is needed. --- Failed during bionic->focal upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chrony 3.2-4ubuntu4.2 ProcVersionSignature: Ubuntu 4.15.0-97.98-lowlatency 4.15.18 Uname: Linux 4.15.0-97-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 11 10:42:36 2020 DpkgTerminalLog: Removing chrony (3.2-4ubuntu4.2) ... Job for systemd-timesyncd.service failed because the control process exited with error code. See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for details. dpkg: error processing package chrony (--remove): installed chrony package post-removal script subprocess returned error exit status 1 ErrorMessage: installed chrony package post-removal script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 2.0.1ubuntu1 SourcePackage: chrony Title: package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed chrony package post-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-11 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872183 Title: package chrony 3.2-4ubuntu4.2 failed to install/upgrade: installed chrony package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1872183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
