I found a case in update-manager where this might have occurred but it was quite some time ago:
$ bzr log -r 1124
------------------------------------------------------------
revno: 1124
committer: Michael Vogt <email address hidden>
branch nick: main
timestamp: Wed 2008-10-15 18:55:42 +0200
message:
DistUpgrade/DistUpgradeController.py:
- reenable cron job on failed downloads too
Walter could you attach the log files from your upgrade,? You'll find them in /var/log/dist-upgrade as they might help find another case where the cronjob's status is not returned.
I found a case in update-manager where this might have occurred but it was quite some time ago:
$ bzr log -r 1124 ------- ------- ------- ------- ------- ------- ------- ---- DistUpgradeCont roller. py:
-------
revno: 1124
committer: Michael Vogt <email address hidden>
branch nick: main
timestamp: Wed 2008-10-15 18:55:42 +0200
message:
DistUpgrade/
- reenable cron job on failed downloads too
Walter could you attach the log files from your upgrade,? You'll find them in /var/log/ dist-upgrade as they might help find another case where the cronjob's status is not returned.