Bug #11532

Clean apt-cacher-ng cache from expired time-based snapshots

Added by bertagaz 2016-06-15 05:26:44 . Updated 2016-07-14 17:03:16 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Tails_2.5
Start date:
2016-06-15
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
269

Description

During the 2016 June sysadmin shift, we noticed that the apt-cacher-ng cache disk was filling up because of expired time-based snapshots. The deletion of this files should be handled automatically to avoid this situation.

Subtasks

History

#1 Updated by intrigeri 2016-07-03 07:45:40

#2 Updated by intrigeri 2016-07-14 05:57:15

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100

Fixed via Puppet manifests + puppet-tails + jenkins-jobs, by not using acng for ISO builds on lizard anyore:

On lizard, the huge majority of what we fetch during an ISO build comes
from local VMs, and is hard to expire on apt-proxy.lizard. So let’s
simply not use acng at all, this shouldn’t be any slower (and might even
be faster).

#3 Updated by intrigeri 2016-07-14 15:14:29

  • Status changed from Resolved to In Progress
  • Assignee set to intrigeri
  • Priority changed from Normal to High
  • % Done changed from 100 to 10

Ooops, that broke the ISO builds on Jenkins.

#4 Updated by intrigeri 2016-07-14 17:03:16

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • Priority changed from High to Normal
  • % Done changed from 10 to 100

Reverted most of the previous implementation, and re-implemented (puppet-tails, bf0a380) in a way that doesn’t break the build.