I ran two Bionic VMs one as-is and one with proposed enabled to get the new
chrony.
One upgrade starts at 3.2-4ubuntu4.2 the other one at 3.2-4ubuntu4.3 from
proposed.
Both run `do-release-upgrade -d`
Both run into bug 1872902
Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1
Removing: chrony
MarkDelete chrony:amd64 < 3.2-4ubuntu4.3 -> 3.5-6ubuntu3 @ii umU Ib > FU=0
Unfixed one ran into:
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
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/chrony.0.crash'
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error
code (1)
The fixed version worked though the upgrade just fine.
Marking verified
P.S. Rbasak mentioned that in this case we might want to shorten the
aging period for the SRU to get more upgrade-tests of the new code on
prior to Focal release. @SRU team do you think that is reasonable and if
so what would be a good time then?
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
