possible race condition with the apt.cron.daily job
Bug #277079 reported by
Michael Vogt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
Medium
|
Michael Vogt | ||
Intrepid |
Fix Released
|
Medium
|
Michael Vogt |
Bug Description
Binary package hint: update-manager
There is a possible race condition when update-manager is run with the daily apt cron job. When "apt-get check" is run it in the cron script to take the lock and rebuild the caches, that may happen between two dpkg invocations in the package installation code.
The fix must:
a) add a workaround during the release upgrade to make sure the apt.cron.daily job is not run (either via a custom config in /etc/apt/
b) add code into the apt cron job to test for the lock without actually taking it (or for a much shorter time than apt-get check that also rebuild the apt pkgcache.bin)
Changed in update-manager: | |
assignee: | nobody → mvo |
importance: | Undecided → Medium |
milestone: | none → ubuntu-8.10 |
status: | New → Triaged |
Changed in update-manager: | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package update-manager - 1:0.93.24
---------------
update-manager (1:0.93.24) intrepid; urgency=low
* DistUpgrade/ DistUpgradeCont roller. py: DistUpgradeAptC drom.py:
- disable the apt.cron.daily script during the upgrade
(LP: #277079)
* DistUpgrade/
- work around the problem that the hardy "apt-cdrom add" will
fail when no uncompressed Packages files are on the CD
(LP: 276349)
-- Michael Vogt <email address hidden> Tue, 14 Oct 2008 16:30:41 +0200